I'm not certain that I understand your situation completely, but I don't see any
issues that wouldn't be handled by using BeginInvoke rather than Invoke. That will
let both UI and process threads proceed without waiting on the other.
In some cases, you might want to use the FireAndForget mechan
> Oh, and the Tablet PC's Ink API fires some events on background
threads...
> Go figure, eh?
Firing events from background threads for consumption in the UI is the
hardest problem (for me) that I face at the moment.
If I have a long running process that needs to invoke events that the UI
has hoo
Right Jade, I'm with you -- that's actually what I meant by leading my last
email with "I feel your pain"... I can be cryptic like that, sometimes. :)
Like you, I don't mind that HWND objects aren't thread-safe (as you say, we
can take responsibility for the locking, if we're so brazen as to writ
