> but thats really bad if i need a blocking message box (like
> g_dialog_run)
Yes, it hurts. But I guess we can create a common helper function which
emulates the behavior of g_dialog_run by waiting for a signal from the
GUI handling code in gtk_main.
/Bo
--
but thats really bad if i need a blocking message box (like
g_dialog_run)
On Sun, 2003-11-30 at 13:39, Bo Lincoln wrote:
> > i have now found the reason. it crashes for some reason because it is
> > called in a different thread. if i wrap it into another function and
> > call it with g_idle_add it
i have now found the reason. it crashes for some reason because it is
called in a different thread. if i wrap it into another function and
call it with g_idle_add it works perfectly. does anyone know how i can
still call it in this function without g_idle_add?
This is the way it is done in the res
On Sat, 2003-11-29 at 02:43, Armin Bauer wrote:
> Hi.
>
> i was working on the some features for the palm plugin when i stumbled
> across an error which i cant fix...
>
> i added a feature to detect if it actually is the correct Palm to sync
> with. if it detects that a different palm has been co
