Re: Is sigc++ emit() thread safe with GTKMM

[Lihling Tzuu <ltzu lle rochester edu>]

Bob,

Thank you for the suggestion.  Glib::Dispatcher is good if no data need to be shipped because it's using signal slot0.  I think if I want to send data along I should use sigcx threadtunnel.

Thanks again,
Lihling

Robert Caryl wrote:

You would be better off to use Glib::Dispatcher to signal your GUI thread from your worker threads.

Bob Caryl
Fiscal Systems,Inc.
256.772.8920 Ext. 108
http://www.fis-cal.com

This email message may contain privileged or confidential information. If you are not the intended recipient, you may not disclose, use, disseminate, distribute, copy or rely on this message or attachment in any way. If you received this email message in error, please return by forwarding the message and its attachment to the sender and then delete the message and its attachment from your computer.

Neither Fiscal Systems, Inc., nor its affiliates, accept any liability for any errors, omissions, corruption or virus in the contents of this message or any attachments that arise as a result of e-mail transmission.

Lihling Tzuu wrote:

I like to use sigc++ signal slot to send data from hardware threads to gtkmm gui. I can mutex lock my emit() calls but I'm wondering if it's thread safe in a gtkmm signal environment? 

Thanks,
Lihling

_______________________________________________
gtkmm-list mailing list
gtkmm-list gnome org
http://mail.gnome.org/mailman/listinfo/gtkmm-list