Re: bonobo_ui_handler_menu_set_toggle_state
- From: John Sullivan <sullivan eazel com>
- To: Ettore Perazzoli <ettore comm2000 it>
- CC: gnome-components-list <gnome-components-list gnome org>
- Subject: Re: bonobo_ui_handler_menu_set_toggle_state
- Date: Mon, 20 Mar 2000 07:26:48 -0800
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.
John
on 3/20/00 6:45 AM, Ettore Perazzoli at ettore@comm2000.it wrote:
> John> Currently it behaves as if the user had selected the menu
> John> item, but this seems like it's the wrong choice. How can a
> John> caller set the state of the checkbox without actually
> John> causing code to run? The same issue exists for the radio
> John> button items.
>
> This is the same way GTK+ widgets behave. Normally in GTK+ you can
> prevent the signal from being delivered with gtk_signal_block(), but
> in the case of Bonobo, of course you cannot do this.
>
> So, yes, I think I agree with you that the call should only change the
> state without triggering the callback.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]