On Apr 24, 2006, at 3:43 PM, Charles Ross wrote:
If that's the case, then why does the above work? Originally, I was
setting the db property in Window.Open, but there were controls
that needed to access the property in their Open handlers, and they
were executing before Window.Open. Creating the above Constructor
solved the problem, i.e., I wasn't getting a NilObjectException
after I added it, whereas I was before. This led me to conclude
that the control Open handlers were executing before the
Window.Open handler.
However, if super.Window executes the control open handlers, the
Constructor above should raise the NilObjectExceptions again, but
it doesn't.
Or am I missing something?
Calling Super.Windows should cause all Open events in controls on the
window to fire.
If you do all your set up for the Window and then call Super.Window
then all the open events will be able to access the Windows
properties safely.
_______________________________________________
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>
