Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

Can we close a Dialog?

Homer Antler
Registered User
Join date: 21 Oct 2006
Posts: 105
12-07-2006 18:21
Hi,

I am working with a Dialog blue menu. Is there a way to close it automatically after certain time? I am working with timer() to get the user's input. After 2 minutes, I want the dialog screen to go away. I am not sure how to close it automatically. It is not a biggie but I thought I would check with the gurus.

Thanks,
Homer
Lazink Maeterlinck
Registered User
Join date: 8 Nov 2005
Posts: 332
12-07-2006 18:46
No, there is no way to close the dialog box on someone's client. What you can do is not accept inputs after a certain time. So the timer event, you set after you open the box, you set how much time you wait for input, if it's not given, in the timer event you close the listen channel. This is good practice anyways as it'll keep your script from continually listening on that channel.
Homer Antler
Registered User
Join date: 21 Oct 2006
Posts: 105
12-07-2006 18:54
From: Lazink Maeterlinck
No, there is no way to close the dialog box on someone's client. What you can do is not accept inputs after a certain time. So the timer event, you set after you open the box, you set how much time you wait for input, if it's not given, in the timer event you close the listen channel. This is good practice anyways as it'll keep your script from continually listening on that channel.


Thank you for your quick comment. Yes I have a timer that times out after 120 seconds and it does not listen afterwards. I just thought it will be nice to close that dialog box as well but I guess I can't. Just trying to be too perfect. :-)

Again thank you.

-Homer
Osgeld Barmy
Registered User
Join date: 22 Mar 2005
Posts: 3,336
12-07-2006 22:27
that would be a nice addition to the llDialog system, maby a timeout option that not only kills the blue box, but also the listener

altho i would hate to think about the overhead if a long dialog tree or a group of ppl hitting the object all at once happened
Newgate Ludd
Out of Chesse Error
Join date: 8 Apr 2005
Posts: 2,103
12-08-2006 01:17
From: Osgeld Barmy
that would be a nice addition to the llDialog system, maby a timeout option that not only kills the blue box, but also the listener

altho i would hate to think about the overhead if a long dialog tree or a group of ppl hitting the object all at once happened


Not sure it would be able to kill the listen since it is not set up as a part of the llDialog call but certainly I'd like to see an optional timeout parameter that would auto kill the dialog.

UPDATE:I have submitted this as proposal 2485
Homer Antler
Registered User
Join date: 21 Oct 2006
Posts: 105
12-08-2006 09:56
From: Osgeld Barmy
that would be a nice addition to the llDialog system, maby a timeout option that not only kills the blue box, but also the listener

altho i would hate to think about the overhead if a long dialog tree or a group of ppl hitting the object all at once happened


Yes I wish we can have this as part of an update.

Newgate, thats great. Lets hope to get this.
Peekay Semyorka
Registered User
Join date: 18 Nov 2006
Posts: 337
12-09-2006 09:23
There is an existing proposal (2448) which discusses revamping the entire dialog system, which would solve closing dialogs, timeouts, the need to even "listen" at all, and other dialog issues.

/13/3e/152183/1.html

Please vote for it instead of splitting votes among several related feature requests.

The original proposal was to add an input field to the dialog system, but we hope the other issues will be considered at the same time, and at least a subset will be acknowledged for future enhancement.

-peekay
Newgate Ludd
Out of Chesse Error
Join date: 8 Apr 2005
Posts: 2,103
12-09-2006 10:25
ahh I did a full scan for dialog related feature proposals (or so I thought) and didnt get anything which is why I put in the proposal.

Although related, this proposal as it stands is not the same as being able to autoremove dialogs. I agree with the basic idea and having read the related thread I would be like to see some of the features suggested although I am not sure the full feature list requested is really viable.