Vinzent Hoefler wrote:
So, the semantics would be about the same as in a signal (apart from the "softer" timing), but you would have much less restrictions in the handler's implementation compared to a real OS signal, which acts more like an interrupt.
Impossible. You'll end with TThread.Synchronize, but without its advantage of knowing in which thread it runs, because the entire *point* of a GUI thread is that it's not doing anything for 99% of the time (waiting for user input only).
Micha _______________________________________________ fpc-devel maillist - fpc-devel@lists.freepascal.org http://lists.freepascal.org/mailman/listinfo/fpc-devel
