Hi George, all,
George Gatling wrote (in part):
>The latency between pressing the sweep button and seeing data
>on the screen is here to stay. What techniques do you expert
>GUIers use to discourage repeat clicks on the sweep button?
>I have had my own ideas such as disable and greying the button...
>using a modal "Please Wait" dialog... I am curious what would
>be considered an elegant or at least widely accepted way
>to handle this sort of delay. ... the delay is 1-2 sec -5 min
I don't know that there is a "standard" way, a lot depends on personal and
corporate style, but I find a combination of disabled & grey with some type
of movement to indicate that a process is on going gives the operator
assurance that the application isn'
t hung while preventing them from
pressing that button (or twiddling that control) again.
For motion I often borrow the spin indicator off the Library Manager under
the LabVIEW tools menu. If you open the Librarian, then hit ctrl-. (Windoze,
YMMV) the VI aborts and you can pillage the parts village at will. If you
click-drag the area between the two upper menus you will get an outline of
an ?mpty" box, which is a picture ring. Double click on that and you'll see
the code segmant that runs the ring. Its in a while loop in the bottom
section of the diagram.
As for Enabled/Disabled-Grey, I got tired of the real-estate taken up by
handling this so I coded up a simple small-icon VI to switch between Enabled
and Disabled-Grey by a boolean input (does anyone use the Disabled without
the grey a large percentage of the time?, just curious). I've attached that
here, for posterity.
Mike Ashe
[Attachment Enabled from boolean.vi, see below]
