> > -Original Message-
> > From: Luca Cappa [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, February 24, 2005 10:56 AM
> > To: Prewitt, Nathan C ERDC-ITL-MS Contractor
> > Subject: Re: Blocking signals
> >
> >
> > Hello Nathan,
> &g
> > -Original Message-
> > From: Luca Cappa [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, February 24, 2005 10:56 AM
> > To: Prewitt, Nathan C ERDC-ITL-MS Contractor
> > Subject: Re: Blocking signals
> >
> >
> > Hello Nathan,
> &g
This is one of the recurring problems in GTK.
If you only want to block your own handlers, the easiest way is to have
a global flags
that every handler checks to determine whether or not it should execute.
It is not elegant, but it's easy and failproof. Of course if you are
trying to block defaul
On Thu, 24 Feb 2005, Prewitt, Nathan C ERDC-ITL-MS Contractor wrote:
>
> I would like to write a generic routine that will set the value of a
> GtkHScale, for example, without it triggering a signal. I have used
> g_signal_handlers_block_by_func() before, but that requires that I know the
>
> -Original Message-
> From: Luca Cappa [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 24, 2005 10:56 AM
> To: Prewitt, Nathan C ERDC-ITL-MS Contractor
> Subject: Re: Blocking signals
>
>
> Hello Nathan,
>
> if in your case a set_value call trigs
I would like to write a generic routine that will set the value of a
GtkHScale, for example, without it triggering a signal. I have used
g_signal_handlers_block_by_func() before, but that requires that I know the
function name. If the routine is generic, I would have a pointer to the
GtkHSca
