No. Not really.
Event structures should not have any code embedded in them that may take a long time to run and block other events. If you do have such a routine, you should move that to another while loop using a producer/consumer architecture with queues. The event structure would just load a command into a queue that the other while loop would dequeue and start working on. The event structure's loop will become quickly available to process other events.
If the second event is one that is intended to interrupt the first routine, then you just need to have the right communication architecture to send to the other loop. This could be another queue command, perhaps a notifier or occurence. A local variable or functional global variable.
Remember that you can't stop any structure in the middle of its process. A while loop can be stopped, but all the code in the while loop must execute before that iteration of the loop is stopped.
