* Qt 3 events - when passing QCustomEvents from a secondary thread (since only the main Qt thread should be allowed to update the gui), make sure it's from the parent of any fork()ed processes, not the child. accomplish this with a pipe() that you write/read the event data to/from (between child and parent). - use postEvent instead of sendEvent. send will send it directly to the widget, and thus the event will be handled in the secondary thread - not what you want. post will post the event to the event queue that is handled solely by the main (gui) thread. - if multiple events are being created from the same place (or using the same variables, etc), do not directly pass in your data with QCustomEvent::setData(). due to postEvent, multiple events are processed together, after a delay. this means that the data for your various events will only point to the _current_ data, and thus you will be end up with multiple events that operate on the same data. instead, create a new object for each event. be sure not to free() this before the event is processed (meaning, not immediately after you post the event), or your the data in the event will end up missing. NOTE: I do not currently know if this is freed by the event handler (as the QCustomEvent is). I'm leaving it unfreed for now, and hoping for the best.