From: zavpublic-spamblock-mac.com
Subject: Re: [DIRECT-L] UI framework code. Radio buttons. 1
Date: February 3, 2007 6:51:41 PM CST
To: DIRECT-L-spamblock-LISTSERV.UARK.EDU
Reply-To: DIRECT-L-spamblock-LISTSERV.UARK.EDU
On Feb 3, 2007, at 5:04 PM, prothero wrote:
Folks:
I'm totally getting Zav's concept of individual UI element states, like buttons, radio buttons, etc.
What I was referring to is kind of a "meta-state". For example, with my slide show presenter
analogy, one state might be:
state 1) no slide shows loaded.
-- the first, next, prev buttons are disabled and the dropdown slide select menu is disabled.
state 2) slide show loaded and first slide is showing
-- the first and prev btn are disabled, the next btn and slide select dropdown are enabled and the select
dropdown has a marker at the first slide (the little marker that shows the selected line when the menu
is opened).
state 3) slide show at a valid slide, but not at start or end
-- all buttons enabled, slide select dropdown is enabled and a marker is at the showing slide.
etc, etc.
Bingo. Parcheesi. Etc...
This approach would require the definition of larger application "states" that have sub-definitions,
of each of the UI element states. So, it would look like a single UI element state, but that state
would apply to the sub-states of individual buttons, checkboxes, menus, etc.
The sub states are independent yet may reflect a certain state of a certain property of group that owns it. Like visibility for example. The visibility of all the radio buttons reflect the visibility of the of the group.
---
Macromedia Director Mailing List (Direct-L)
List Administrator: Eve M. Owens (emowens-spamblock-theserver.uark.edu)
To SUBSCRIBE or to UNSUBSCRIBE go to
and click on
"Join or leave the list (or change settings)"
For list archives