Since you want to pass in parameters my thinking was that it would be
easier to initialize and set the values for controls etc from some
type of Init Method *after* the controls open events fire.
A windows Constructor event fires *before* the open events of the
controls, so that may be an issue.
Oh - if you do use the Constructor method, make sure to add
Super.Window()
as the last line of the constructor or else the windows open event
won't fire
- Jay
On Apr 27, 2006, at 10:49 AM, Jeff Edwards wrote:
Yes . . I see your methodology should work well. I do appreciate
the clarification. I also appreciate the answer from Karen. This
has given me the nudge to look up constructors.
Jeff
On 27/04/2006, at 10:38 PM, Jay Wooten wrote:
Yes - correct. When the window "opens" the open event fires -
however, take whatever code you have the in the open event, and
put it into the Init Method.
Use the Init method to configure the window, controls etc and when
all of that is done, call self.Show or extermally w.show
That way it will be ready for the user when it is shown.
- Jay
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
