Jim
>As you so keenly pointed out, if I only have one caller and many
>subpanels it is relatively easy to implement it once. However, we
>currently have 61 User GUIS that use about 15 GUIS repeatedly. I don't
>want clutter up my GUIS with subpanel stuff. That can be handled by
>another object very cleanly. My plan was to use a single subpanel and
>inserted the currently active VI or subVI. However, in order for this
>to work, the VI itself needs to call my method which removes anything
>that might be there, pushes it onto the stack, and puts the new caller
>in the subpanel.
>subpanels it is relatively easy to implement it once. However, we
>currently have 61 User GUIS that use about 15 GUIS repeatedly. I don't
>want clutter up my GUIS with subpanel stuff. That can be handled by
>another object very cleanly. My plan was to use a single subpanel and
>inserted the currently active VI or subVI. However, in order for this
>to work, the VI itself needs to call my method which removes anything
>that might be there, pushes it onto the stack, and puts the new caller
>in the subpanel.
If I understand what you described, you can create an object to handle subpanel management. While I insert VIs in my subpanel from the caller, I dont believe it is an absolute requirement (I might be wrong). Once you get a subpanel reference you should be able to do all the process from within another VI. So what you could do is having each top level VI register its subpanel(s) reference(s) (along maybe the top level name for example) in an object. Then when the GUIS need to insert itself in the caller (top level) it will call a "Subpanel Manager" that will do all the work using the registered subpanel refs.
For all my subpanel work I used a subpanel manager with method, and all the code is in the manager and it work well. I have not try to insert VI in subpanel from another VI, but I dont see why it should not work.
Good Luck
PJM
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
