I used to use signals for a similar thing... its not exactly multi-threading... but its like a 1ms timer... things go in order of what was send... hard to explain but if two aliases are called and they both split and do 3 things each, they will more likely go ababab rather than the default aaabbb...
Actually, as sat tested, SIGNAL does not guarantee execution order after events (sorry). It uses the asynchronous PostMessage call from the Windows API, which is thread dependent.
PostMessage Function
The PostMessage function places (posts) a message in the message queue associated with the thread that created the specified window and returns without waiting for the thread to process the message.
This actually makes it very much like multithreading-- ie. you do NOT get order.. and if you're thinking "oh I don't get order with multithreading?" well yea, that's why you wouldn't want it in the first place.
