Re: Introduction of the TnyLockable

[Philip Van Hoof <spam pvanhoof be>]

On Mon, 2007-01-22 at 12:16 +0100, Philip Van Hoof wrote:
> Issuing signals will always have to be done after you g_idle out of the
> function. Well it doesn't have to be done that way, but then will your
> signal handler run in the thread (and then you would need the gdk
> locking, which is probably not what you want).
> 
> That's because the function is always launched in a thread.

Also note that it will most likely always be launched in a thread too.
That's because there's simply no other way to otherwise make connecting
async.

Unless you manage to let the functions happen on the mainloop, and let
the/a worker thread wait for that. I tried but I didn't manage to get
that working (in any way, and I did try really a lot). 

Good luck.

> so 
> 
> static gboolean signal_launcher (gpointer data)
> {
> 	g_signal_emit (...);
> 
> 	return FALSE;
> }
> 
> static char* my_get_pass_func (TnyAccount *a, ...)
> {
> 	g_idle_add (signal_launcher, ...)
> 
> 	return "the password";
> }
> 
> 
> On Mon, 2007-01-22 at 10:51 +0100, Sergio Villar Senin wrote:
> > Philip Van Hoof wrote:
> > > Some (major) improvements have happened on this ..
> > > 
> > > But there's still some issues with it too.
> > 
> > Yes, for example, this new main loop seems not to work very well, I had
> > some problems issuing signals inside the get_password_func stuff.
> > 
> > Br
> > _______________________________________________
> > tinymail-devel-list mailing list
> > tinymail-devel-list gnome org
> > http://mail.gnome.org/mailman/listinfo/tinymail-devel-list
> 
> _______________________________________________
> tinymail-devel-list mailing list
> tinymail-devel-list gnome org
> http://mail.gnome.org/mailman/listinfo/tinymail-devel-list