I'm wondering what is the recommended way of handling a lot of dialog
boxes in applications. There are a couple of way of handling this that
I've thought of but I don't know what would be considered best:
1) A separate stack for each dialog.
Pros: Sizing, function (information only,
What kind of dialog boxes do you needing to show?
My personal take is that dialog boxes should be kept as simple as
possible, and therefore the built-in answer and ask commands cover
about 90% of my needs plus a small number of separate stacks for the
remaining more complex ones.
Ian
Hi Len,
First I have to say that I try to minimize dialogs use.
In many cases, I use a group on the current card but with a darker
background because, as a user, I hate to have hundreds windows, all
different, that show up and have to be closed as you can see them in
MS Word for instance.
On 20/02/08 at 07:58 -0600 Len Morgan apparently wrote:
I'm wondering what is the recommended way of handling a lot of
dialog boxes in applications. There are a couple of way of handling
this that I've thought of but I don't know what would be considered
best:
There is no single best
Len and Robert:
Another solution is to designate one card in your stack as the dialog
card, title it Information, and place a field, a Cancel button, and
an OK button on it. Then place the dialog information into the field
by script as shown below. This method is very flexible and
Thanks to everyone for their responses. It appears that:
1) There are MANY ways to handle dialog boxes (I knew that before)
2) The is NO best way to do it.
I guess Rev's blessing of flexibility can also be a curse! :-)
len
___
use-revolution
