Hi Carlos and Phil and Arnaud,
On Jan 2, 2007, at 1:11 PM, Carlos M wrote:
Phil's suggestion is a good one and you can do more with that
approach:
- You can for example create a different class for each window (2
and 3) if you
have different properties on each window.
- You can create methods on the classes to execute code on Window 2
and 3, from
Window 1.
- You can even create new events for each window and fire them from
window 1.
If you have common code for both windows 2 and 3 you can create a
main class
with the common code and then create subclasses of the main class
for each
window to implement specific code for each one.
If Window 2 and 3 have some methods that are specific for an app
and that you
don't want to include on the classes but you need to execute them
via Window 1,
you can implement a class interface for each Window (2 and 3).
I'm wrapping my mind around the concept, as I found a very good
reference up on Getting Started Archive. Something written back in
2005 by Mark Nutter; http://support.realsoftware.com/listarchives/
gettingstarted/2005-10/msg00796.html.
This gives a much better information than what some others around
here were offering.
It certainly isn't blatantly obvious how to go about achieving what
I'm after, but that item was a big help.
Have a Happy New Year.
Regards,
Chuck
_______________________________________________
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>
