event structure stop

[wiebe@CARYA]

I've done this like a milion times! It's not very "pure", but how convenient would it be if the event structure itself kept looping until stopped?

This should be optional, like in the for loop ("Conditional Terminal").  For the event stucture, it wwhould be nice if wiring it is optional (unwired means keep looping), or that you can show\hide it on a per event basis.

Regards,

Wiebe.

[Intaris]

User Events.  Unregister for events after exiting the event structure.  Job done.

I have also missed the functionality to be able to deregister certain statically linked UI events in the past.  UI Blocking with an event structure which has been exited (not a common use I admit) can lead to lockups because it's not possible to tell the Event structure to STOP listening to certain UI events (and then blocking the UI until they're handled.  Oops).

[Mads]

When the event structure first came out I have to say that I intuitively expected it to run continously until it received a stop command. Shift registers etc. would be nice to have as an option on the border just like for the loops yes.

I do not see why you would need to differentiate between a "looping" event structure and a non-looping (other than for backwards compatibility), it would be way the it works. You just always have to handle the stopping of it. Old code would have that stop set to true by default when converted to the new version...

[wiebe@CARYA]

>User Events.  Unregister for events after exiting the event structure.  Job done.

Not sure how this would help?

[ToeCutter]

Feels messy to me- and doesn't save any effort.

[Intaris]

Misunderstood the OP, sorry.  I thought it wanted to "stop" the Event structure in a completely different context. (Stop it responding to events).

[Darren]

Any idea that has received less than 4 kudos within 4 years after posting will be automatically declined.