Multi-user access to context-sensitive dialogs
andromedaquonset at gmail.com
Tue Jul 28 08:02:19 PDT 2009
As some have suggested, you could use a list. I would be worried
about the extra complications and storage requirements, too. I
haven't tried this approach before,a nd i would want to think about
it before i decided what complications it can bring.
I have one product that invokes a timer when a particular prim is
touched to activate a dialog. Normally, the prim is yellow, but
during the time that the timer is active, the prim is red. If
another AV touches the prim while it is red, he receives a warning
dialog box that says the product is in use and to please wait.
At 06:06 AM 7/28/2009, you wrote:
>Does anyone have a neat way of handling multiple-user access to
>dialogs where context between dialog calls is required? I have a
>fairly complex hierarchy menu structure where I need to save context
>between calls to llDialog as the user navigates down through the
>menu levels. It wasn't a problem that really surfaced until I rezzed
>a demo version of the object at my store and regularly get multiple
>avatars accessing it at the same time.
>At the moment I have all the llDialog calls in one script and a
>single set of global variables holding the context - great design
>for single-user access but nothing more! Having context variables
>per agent in a look-up list would work, but would be a lot of work
>to retrofit, a possible nightmare to manage the list, and seems a
>bit overkill. Is there a better solution? eg Multiple copies of the
>dialog script controlled by link messages fed from a central script
>with a touch_start event handler maybe? I guess there'd be similar
>issues effectively managing the "pool" of available dialog scripts
>but it'd end up being a generic solution I could hopefully utilise
>in other projects.
>The other option of course is to make my object effectively single
>user and block access to the dialogs while in use for a period of
>time. But how much time when there seems no way of knowing when a
>dialog has been dismissed??!
More information about the secondlifescripters