[Gtk-sharp-list] Application.Invoke

Hi there, I use a thread, wich does some Application.Invoke. The Thread itself works properly and the invokes are done. But ... the invoked delegates are only executed when some keystrokes or mousemoves are done. I also tried to use TimeoutHandlers, but received the same behavior. Some suggest

Re: [Gtk-sharp-list] Application.Invoke

ation's mainwindow as one activity-fake for all these processes. Thank's a lot for brain sharing :-) Robby -- View this message in context: http://www.nabble.com/-Gtk-sharp-list--Application.Invoke-tf2944511.html#a8239426 Sent from the Mono - Gtk#

Re: [Gtk-sharp-list] Application.Invoke

On 1/9/07, Robert Schillinger <[EMAIL PROTECTED]> wrote: > the invoked delegates are only executed when some keystrokes or mousemoves > are done. I had a similar problem, too. To workaround it, I added a timeout that forces the execution just like mouse movement and other events do. Here's a snipp

[Gtk-sharp-list] Application.Invoke

Hi there, I use a thread, wich does some Application.Invoke. The Thread itself works properly and the invokes are done. But ... the invoked delegates are only executed when some keystrokes or mousemoves are done. I also tried to use TimeoutHandlers, but received the same behavior. Some suggestio

Re: [Gtk-sharp-list] Application.Invoke and threads: strangebehavior

Hello, > Thanks Miguel, > > Now I have tried to use a little C program (attached) which uses printf > and sleep(1). The usage is 'foo 4' and prints 4 strings, one every second. > > The situation is just the same, I can't understand why the command ping > works fine and my foo program not. The st

Re: [Gtk-sharp-list] Application.Invoke and threads: strangebehavior

> The problem is that the value of "tmp" is shared (captured) and as soon > as you queue the delegate, tmp will be reloaded with the next value from > ReadLine. Thanks Miguel, Now I have tried to use a little C program (attached) which uses printf and sleep(1). The usage is 'foo 4' and prints 4 s

Re: [Gtk-sharp-list] Application.Invoke and threads: strange behavior

Hey, > > The problem is that the value of "tmp" is shared (captured) and as soon > > as you queue the delegate, tmp will be reloaded with the next value from > > ReadLine. > > > > So could this be a 2.0 usecase for an Application.Invoke that takes a > defined parameter? :) He could use the curr

Re: [Gtk-sharp-list] Application.Invoke and threads: strange behavior

> So could this be a 2.0 usecase for an Application.Invoke that takes a > defined parameter? :) > > --Todd Please commit the patch. I vote for it. :-) Meanwhile I have fixed my problem changing my ThreadFunc as pasted. I'm sure this isn't the most "best practice" to do it, do you know another wa

Re: [Gtk-sharp-list] Application.Invoke and threads: strange behavior

On Tue, 2005-10-18 at 11:32 -0400, Miguel de Icaza wrote: > Hello, > > > The execution of the program shows different outputs in the TextView and > > the console. > > It seems like the string 'tmp' forgets its last values inside the delegate. > > The problem is that the value of "tmp" is shared (

Re: [Gtk-sharp-list] Application.Invoke and threads: strange behavior

Hello, > The execution of the program shows different outputs in the TextView and > the console. > It seems like the string 'tmp' forgets its last values inside the delegate. The problem is that the value of "tmp" is shared (captured) and as soon as you queue the delegate, tmp will be reloaded wi

[Gtk-sharp-list] Application.Invoke and threads: strange behavior

Hi, Attached is a very little Gtk# example which uses a Thread to execute the process 'ping 127.0.0.1 -c 7' and refresh both the standard output and a TextView. It can be compiled with mcs or gmcs with $ mcs -pkg:gtk-sharp-2.0 test.cs The execution of the program shows different outputs in the T