llRequestPermissions Dialog Timeout

[GManB]

llRequestPermissions() documentation says the permissions dialog never times out. Yet, it does. When requesting PERMISSION_ATTACH permission users are given three choices in the dialog, Yes, No, Block. Selecting 'Yes' generates a run_time_permissions event with a perm flag of PERMISSION_ATTACH. How/what/where can I catch an event if the user answers 'No' or 'Block' or, worse yet, just lets the dialog expire?

Thanks,

G

[Rolig Loon]

You cannot.  Your script will respond to the buttons that you build into the dialog box but will be unaware of anything that happens when a user clicks "No" or "Block".

Your dialog box will remain open and its buttons will remain active indefinitely, until the user click on one of the buttons you provided.  If you want the dialog to appear top remain open after that, you will have to re-open it with a fresh call to llDialog.  You can use a timer event to make your buttons non-responsive after a time, but you cannopt close the dialog box with LSL.  The best move is to advise the user to close it when the timer disables the buttons.

[GManB]

6 minutes ago, Rolig Loon said:

You cannot.  Your script will respond to the buttons that you build into the dialog box but will be unaware of anything that happens when a user clicks "No" or "Block".

This isn't my dialog that I crated with llDialog(). It is the automatically generated one from llRequestPermissions(). However, do the same semantics apply? I.e., no event is generated to the script calling llRequestPermissions() for any of the three cases, No, Block, or dialog times out and disappears. (I know the doc says the dialog doesn't time out but maybe the are referring to ones generated by llDialog()).

My guess is that I'll just have the script wait for a while and then call llDie().

G

[Rolig Loon]

Oh, right.  As far as I know, that dialog box requesting permissions will stay open forever, until you grant permissions.  It will fade, though, the way that group notices and several other things do. You can't see it unless you click on the little box that holds all your unanswered notices.  And as with the llDialog - generated box, the "Block" button doesn't trigger any event that LSL can make use of.  The "Yes" and "No" buttons flip bits that LSL reads if you use llGetPermissions() or ask if (perm & get_your_favorite_permission), and then they close the box. 

[GManB]

Ok, thanks. That clears up my misunderstanding!

Thanks,

G

[Wulfie Reanimator]

9 hours ago, GManB said:

How/what/where can I catch an event if the user answers 'No'

The "No" button triggers run_time_permissions as well. The value of the given permissions will be 0.

And Rolig is correct, the permission dialog will stay open forever.