I don't think you can include Application Overview in your standalone, but you can certainly include the functionality that you are looking for. You can just create a palette or group, populate it with check boxes for each group, either before building or dynamically when your app starts, and use scripts to hide & show groups based on the check boxes. If the groups are in a separate sub-stack, you can save the stack so your settings stay stuck. Otherwise, you will need to save the settings in a separate file so that you can restore it when the app opens.

Cheers,
Sarah

On Thursday, February 6, 2003, at 07:58 pm, erik hansen wrote:

thanks again for all the help.

my HP app has a menu "btns" and a menu "flds"
that allow the user to hide/show controls on the
"desktop" (card) while they work. each control or
proto-group of controls had a checkmark for each
menuItem. the settings were stored when the page
was closed.

in RR all of this is taken care of in Application
 Overview. better.

the query: in a standalone, is there any way for
the user to utilize groups, Application Overview,
etc. to hide/show controls as needed?

if yes, great!
if no, the work was not in vain!

=====
[EMAIL PROTECTED]    http://www.erikhansen.org

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution


_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to