Event handlers and state changes
meijer78 at gmail.com
Tue Jan 20 07:05:06 PST 2009
2009/1/20 <intel81 at gmail.com>:
> 2009/1/20 GCI38 <gci38 at aliceadsl.fr>:
>> Details must be clarified: (source = the wiki)
>> a) When a "state target" is encountered at runtime: the event queue is
>> b) in the above case the timer event clock is NOT cleared;
>> a + b = c) When a "state target" is executed, if the event queue contains
>> timer events they are lost, but the timer can produces new events.
> ...so the event *handler* persists, as I said ;-)
When splitting hairs, note that an event handler, that which handles
an event, is your code ;-) What you mean to say is better described by
the phrase "event subscription".
> My original question was:
>> > Besides timer(), are there any other event handlers that persist
>> > across state changes?
> it doesn't seem so.
The timer is the only event subscription that isn't automatically
cancelled by a state change.
More information about the secondlifescripters