Christian Ulrich wrote:
Vincent wrote:
I found a little time to look at this patch.
First:
I doubt the general usefulness of having the applicationtype as member
of TApplicationProperties. TApplicationProperties are part of a from,
which is created at its earliest *after* the call to
Application.Initialize. So generally the ApplicationType isn't changed
until known after the call to TWidgetSet.Create *and*
TWidgetSet.AppInit. This limits its usefulness.
why does this limit its usefullness ? when we set it in the projectoptions,
its also set only on appstart.
I think it would be better to set the ApplicationType in the Project
Options as part of the Application Settings groupbox. The IDE would
add/edit/remove the
Application.ApplicationType := atDesktop;
line just before Application.Initialize in the .lpr file.
When it initially got proposed to put it in TApplicationProperties I
didn't realize the consequences.
I agree on Vincent about the usefullness. Further, I think placing a
TApplicationProperties on a form is not really OO.
What if the form gets created later, what if the form isn't created at
all, what if more than one instance of the form is created ?
Part of the application is already running.
What I thing what would be nice to have is something DataModule alike
appearance of the application object.
So that you can there set your properties, place data component on it
etc. When the Application instance is created (or initialized), this
info is read. In this case, the IDE doesn't have to modify the project
sourcecode and you don't have to cludge with a external properties
component.
yes, maybe what schould i do ? schould i remove it from
TApplicationProperties ?
If that part of the patch isn't applied, then you don't have to do
anything :)
Marc
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
