robby.schillinger at t-online.de
Tue Jan 9 09:55:19 EST 2007
That's similar to the workaround, I was just trying :-)
First I tried to replace the Application.Invoke completelely by a
GLib.Timeout.add. But since I don't exactly know how much time the thread on
different machines will use, that's not a really good solution.
It could be invoked again before the preceeding run terminates and so I
would get some less amusing "locking features" ;-)
Now there are currently 9 of these threads running, which continously scroll
some text like a newsticker over the screen. So I decided to start that
TimoutHandler in the application's mainwindow as one activity-fake for all
Thank's a lot for brain sharing :-)
View this message in context: http://www.nabble.com/-Gtk-sharp-list--Application.Invoke-tf2944511.html#a8239426
Sent from the Mono - Gtk# mailing list archive at Nabble.com.
More information about the Gtk-sharp-list