Re: Using Notification to track component creation...
From: Bruce Roberts (ber_at_bounceitattcanada.xnet)
Date: 02/01/05
- Next message: Phil Hansen: "Image component"
- Previous message: Skybuck Flying: "Re: The Debug Game: Russian Roulette"
- In reply to: Raptor: "Re: Using Notification to track component creation..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 1 Feb 2005 11:43:26 -0500
"Raptor" <bogus@none.com> wrote in message
news:ctm9db0150f@news2.newsguy.com...
> First, though, I'd like to see if a reliable drop-onto-stock-form
> unit/component solution can be achieved, even if not optimal, for
> educational reasons if nothing else. Unless I'm failing to understand
> something, creating a custom form descendant seems a project-wide approach
> instead of a component approach.
Forms are really like any other visual control. There are some differences
as far as the Delphi IDE and streaming mechanism are concerned, but
logically one should approach them as one does any other component. The
advantage of using form inheritance is that it can be easily applied to
every form in a project. The disadvantage, IMO, is that the form needs
detailed knowledge of the component types it owns. Dropping an unknown
control onto a translatable form may mean that the control is not (fully)
translated. I don't think though that there is any way out of this dilemma.
Even if the translation is done by each component, one may still have
problems with new controls.
- Next message: Phil Hansen: "Image component"
- Previous message: Skybuck Flying: "Re: The Debug Game: Russian Roulette"
- In reply to: Raptor: "Re: Using Notification to track component creation..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
