Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Active document wrapper
Message
 
To
29/04/2002 00:58:30
John Ryan
Captain-Cooker Appreciation Society
Taumata Whakatangi ..., New Zealand
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00647562
Message ID:
00650414
Views:
33
>Michael
>
>Perhaps I'm missing something... can't you create a Montage Form class that stores subforms as an array and has appropriate methods to refresh, create and destroy subforms. Nesting can be handled by showwindow property. That way you could mimic a montage screen within a montage screen or a browser session or whatever without having to worry about ActiveDocs. If you use private datasessions and form properties rather than global settings, or give each form a settings cursor containing session-specific data, this should work well.
>
>HTH
>
>Regards
>
>JR

John,

Sure, I could rewrite the whole application, introducing complications all over the place just to deal with the possibility of nested montages, but that is not such a clean, simple change. I don't think you are right about simply using the ShowWindow Property to cope with the general nesting problem, because this only can achieve one level of nesting. You can use ShowWindow to instantiate a child form within a top-level form, but not to keep on going deeper into the child form. ACTIVATE WINDOW ... IN WINDOW ... can go deeper, but this is cumbersome.

Likewise, I could try to come up with various kludges to deal with every other asymmetry of VFP, but it just makes the application more and more complex. There are a lot of settings and things that are not scoped to the current data session. What you propose requires that I systematically eradicate every use of a global VFP resource and provide an equivalent localized functionality. This is not a trivial task.

Consider again the analogy to private data sessions. Sure, we could (and did) cope without them by providing logic to carefully manage workspaces so as to avoid conflicts between independent forms and sub-applications, but didn't life get a lot easier when private data sessions allowed us to forget about those complications? The same thing goes for ActiveDocs: they offer a much simpler solution that makes plenty of sense for applications like mine. The clean separation of basic features from recursive complications is a major simplification in the overall application design.

Mike
Montage

"Free at last..."
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform