On-Off-button - Showing State

[sic0048]

Ron is right, but you might not understand the data portion of his thread, so I wanted to make a comment about that.

When you name a widget and you bring up the action portion of the widget (where you create your commands). Under the CMD button (where most of your commands are probably started - like fieldrwrite, etc) you will see the name of each widget. Choose the widget you wish to hide/show and select that choice on the menu. Keep in mind that "visibility" means just that. If visibility is true - then you will see the widget. If visibility is false, then you will not see the widget.

You'll have to make current widget visible (true) and the rest in the stack not visible (false) and do this for all widgets in the stack. So every widget will have every other widget somehow listed in the command area - either hiding or showing. This is what Ron's data portion was showing. That one widget's action commands were making the one widget show and the rest not show. As you can see, it takes a little time to set up, but works great when it is.

[gizmosrcool]

I think I have it. One thing though.

On my main template it has three overlays. A header at the top, footer at the bottom, and a main one in the middle. the main one gets updated when you choose TV, DVD, Weather, etc.

The header has current zone info, weather stats, time. The footer has common TV and receiver stuff. Power, Mute, Channel, etc.

The one thing I find challenging is that I had a button up the header to change the zone, but it would not immediately affect the check box widget in the overlay footer, unless you reloaded the footer. It seems when your in an overlay, you can only mess with it and changes to Gvar's do not necessarily refresh stuff in other overlays which may be located in other templates.

I got around it by placing it in the main template and after loading a pop up to change zones, I reload the header and footer overlays. Those individual overlays take care of updating any widget on it that needs updating.

Thanks everyone for all the help.

[Dean Roddey]

It seems when your in an overlay, you can only mess with it and changes to Gvar's do not necessarily refresh stuff in other overlays which may be located in other templates.

Nothing updates based on variables. They are just storage for values. Fields are the only thing that can drive any visual changes automatically. Any changes caused by variables are ones that you initiate yourself based on your looking at the variables and doing things to widgets.

Your change was the appropriate one.

[jrlewis]

But a popup or popuout can be made to fit into the style of the interfaces, which is generally nicer. And I think that those are only available if you are a power user or administrator, right? If so, they wouldn't work in a kiosk style system where you log the IV in as a limited user.

Good point about the compatability of the interface look. Maybe I missed it somewhere, but aren't popups and popouts always available in the interface regardless of the user?

[Dean Roddey]

Yes, popups and popouts are always available, since you decide when they are available. The direct setting thing is only for power/admins since it can be used to change something independently of other things that may be required to change at the same time.

[jrlewis]

The way you wrote that I thought you were talking about the popups. I was under the impression you could set the level of access for direct writes using a minimum user level from the dropdown right below the checkbox for allowing direct writes.

[Dean Roddey]

I was under the impression you could set the level of access for direct writes using a minimum user level from the dropdown right below the checkbox for allowing direct writes.

Oops, yeh, that's true. I'd not thought about that stuff for a good while.

[jrlewis]

I hear you. My brain has room for a finite amount of information and the rest has to go into backup or be purged. Its usually there...but not always readily accessible.