Why I don't like llDialog()

I've noticed some posts on using llDialog to avoid lag, however, I believe that llInstantMessage() or llWhisper() are better for the user because then they don't have to close a million boxes when they are done. I NEVER ever use llListen(0,"","","" of course, however, until LSL comes up with a way to close dialog boxes from the script not the user, I plan on sticking to IMs.

Agreed. llDialog is getting overused. llOwnerSay or just touch on an appropriate prim-built control panel is often a far better alternative. To take an actual example, Blackjack with dialogs is less than enjoyable... your attention is constantly drawn from the cards to the top right of the screen, and there are simply TOO many dialogs.

As ever, UI design is a black art. But simple, comprehensive testing should prove to the creator not just whether "it works" but whether it is pleasant to use.

Just my 2c

/esc

Using llDialog for output is kinda stupid and does force people to close a lot of boxes.
But for input, it's pretty good, since the box closes automatically when you press a button.
Without llDialog, you force the user to read through a manual and memorize commands.
Not my idea of usability, unless you're catering to hardcore CLI freaks.

llDialog is one of many bad choices that are available to us.

We desperately need for LL to provide better ways to make both 2D and 3D user interfaces.

Well sure, appropriate use is fine, Eggy, as you point out. My agreement was with the rampant inappropriate use of the super-clever llDialog. Almost as if, once discovered, people use nothing else!

In which case, place your vote here:
https://secondlife.com/vote/index.php?get_id=288



/esc

LOL I don't want to derail this discussion, but...

it would be really nice if we could get the coordinates for the touch as well.

Indeed, I agree. Either, or ideally both, as they have different applicability, and as discussed here:

/54/b0/44088/1.html

/esc

yes, however you need to set up two listens(), one for channel 0 and one for the chat channel, because when users click a button two fast, often the script doesn't hear it, forcing them to type in a reply. This isn't that bad, but my main point was talking about llDialogs where the only button was OK, making them an annoyance.

Buttons (whether in a dialog or on a prim) are useful if you are presenting the user a set of discrete choices. However, there are many many kinds of data that does not lend itself well to buttons. If you want to input a numeric value for example, or some text, buttons are often not the best choice.

One useful method input is a wizard-style "conversation" with the user. The user activates, for example, a configuration system by clicking on the object; the wizard can ask a question via chat or IM -- something like: "What text should I display? For example, say 'Hello world!'". The user answers in the normal chat window.

A wizard interface also shares the advantage of dialogs in that it does not require the user to memorize commands or read a long manual.

Of couse for lag considerations it is important that the wizard starts to listen only when activated via a touch, and when the wizard is done, it closes the active listen.