|
Paradigm Brodsky
Hmmm, How do I set this?
Join date: 28 Apr 2004
Posts: 206
|
08-05-2004 16:50
OK here is my question.
I have two or more states in my script. If I create a listen in one state, is that listen still active in memory when the script triggers a different state?
What if I save the listener in a global handle like:
---------------
integer handle1;
.. yadda yadda ...
handle1 = llListen(yadda yadda);
-------------
But wait, the handle just holds the value returned by the listener, not the actual listener. Right??
So I guess the answer is no then. Am I right?
|
|
Christopher Omega
Oxymoron
Join date: 28 Mar 2003
Posts: 1,828
|
Re: States and listens
08-05-2004 17:17
From: someone Originally posted by Paradigm Brodsky
OK here is my question.
I have two or more states in my script. If I create a listen in one state, is that listen still active in memory when the script triggers a different state? No, all listen handles are automatically removed when state changes. From: someone Originally posted by Paradigm Brodsky
What if I save the listener in a global handle like:
---------------
integer handle1;
.. yadda yadda ...
handle1 = llListen(yadda yadda);
-------------
But wait, the handle just holds the value returned by the listener, not the actual listener. Right??
So I guess the answer is no then. Am I right? The integer returned from llListen simply allows you to identify the listen when using llListenRemove/llListenControl; storing it in a global variable has no effect on how the listen functions if state changes. If you change state, the integer simply doesn't point to an active listen handle; its just a plain old integer. ==Chris |