search for: tcl_do

For processing events, RGtk2 has moved away from using the old tcl_do hack and now synchronizes on the Windows event loop. In Rgui.exe this works fine (well mostly), but in Rterm.exe, users report the following warning from GLib: "main loop already active in another thread". The most obvious way this could occur is if the Windows event loop were iterating i...

Hi Graham, Your guess is right. The event loop stuff is handled differently on Windows than on Unix-like OSes. There is a hook, called tcl_do that is hard-coded into the R Windows GUI. It is called whenever the console is idle. RGtk2 is able to hook into that to process GTK+ events. The problem is that the two packages replace each other's handler. So in this case tcltk is blocking GTK+ from processing its events. Perhaps these pack...

...an abstraction around the event loop handling, so that package code is the same across platforms. I understand that's a non-trivial task. Michael > > > L. > > > > 2008/8/13 Michael Lawrence <mflawren@fhcrc.org>: > > This is almost certainly due to the lack of tcl_do in R devel. I fixed > this > > in RGtk2 by using multiple threads and synchronizing on the Windows event > > loop. If the maintainer wants an example of how to do this, he can check > out > > RGtk2. I will upload the new version to CRAN today. > > > > Michael &gt...