Re: Using (or not using) sigc::mem_fun with the G_CALLBACK macro
- From: Murray Cumming <murrayc murrayc com>
- To: Bob Caryl <bob fis-cal com>
- Cc: gtkmm-list <gtkmm-list gnome org>, paul linuxaudiosystems com
- Subject: Re: Using (or not using) sigc::mem_fun with the G_CALLBACK macro
- Date: Thu, 16 Jun 2005 13:42:00 +0200
On Thu, 2005-06-16 at 06:08 -0500, Bob Caryl wrote:
> Murray Cumming wrote:
>
> >And if you must provided a C function pointer, you'll need to provide a
> >pointer to a static method (or global function) and the state
> >information as user_data. See the various SignalProxy classes, for
> >instance, in TreeSelection.
> >
> >
> >
> In other words, the way I've done it (separate executable invoked via
> fork, execv) is the only thread safe way to do this until GtkHTML has a
> C++ wrapper.
I don't see how threads have anything to do with this.
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]