Re: bonobo_ui_handler_menu_set_toggle_state

[Nat Friedman <nat helixcode com>]

James Antill <james@and.org> writes:

> Nat Friedman <nat@helixcode.com> writes:
> 
> > John Sullivan <sullivan@eazel.com> writes:
> > 
> > > Ettore, thanks for youre reply.
> > > 
> > > I have at least for now used a workaround for this problem. Before calling
> > > set_toggle_state I save the callback function and then set the callback
> > > function to NULL. Then I call set_toggle_state. Then I restore the callback
> > > function.
> > > 
> > > This works for my purposes, but feels like a hack. However, I will defer to
> > > the Bonobo maintainers the question of whether or not set_toggle_state
> > > should trigger the callback function.
> > 
> > This is gross.  You're right; let's change the behavior so that it
> > doesn't emit the signal.  Please add a note to this effect at the head
> > of the method, though, so that people who expect the Gtk behavior
> > don't get confused.
> 
>  But what happens if you are triggering other GUI elements based upon
> the radio buttons (I can imagine it would happen more often with check

If you're triggering other things off the callback, and you want them
triggered, then you need to manually invoke the callback when you
modify the toggle/radio state.

>  I'm guessing it's not possible to pass a flag saying this UI change
> is "interactive" while that one isn't ?

Sure, this is possible.  But why?

Nat