> If it's always identical we could just modify it and leave it there as a
> class helper function.
true
> Well I tracked this down till LyXView::showState which updates the right
> things and the toolbar than is updated. If showState is not called there
> is no update at all! IMO there has some logic to be changed, but I've no
> clue where to start looking at this, maybe we should just wait for Jean-Marcs
> return and hear what wise things he has to tell us :)
I suppose that we need to call update after each action is executed
regardless of the source of the action (menu, toolbar, pipe).
> Then now I get some gtk errors when I'm inside a tabular like this:
>
> Gtk-WARNING **: invalid cast from `GtkMenuItem' to `GtkCheckMenuItem'
>
> Gtk-CRITICAL **: file gtkcheckmenuitem.c: line 144 (gtk_check_menu_item_set_active):
> assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed.
>
> Gtk-WARNING **: invalid cast from `GtkMenuItem' to `GtkCheckMenuItem'
>
> Gtk-CRITICAL **: file gtkcheckmenuitem.c: line 144 (gtk_check_menu_item_set_active):
> assertion `GTK_IS_CHECK_MENU_ITEM (check_menu_item)' failed.
>
> Could you have a look at them?
Well, I can't reproduce it (or I don't undestand how I can get into this
"tabular" thing :) ). However, if you know any LyX action which changes
its state after you enter tabular from "plain action" to action which can
be toggled (LyXFunc::ToggleOn or LyXFunc::ToggleOff ) then you should know
the cause. Namely, when the menu is composed I use either regular or if
the action is toggled on/off --- GtkCheckMenuItem. Do you know any means
how can I know on beforehand whether the action is toggleable?
Marko
