Definitely. You may want to experiment with the new AtPoint LyXAction
flag.
Done.
Some other points:
1. The Inset::edit functions should not be implemented other than for
InsetCollapsables (which are editable).
2. LFUN_MOUSE_RELEASE of insets should dispatch an LFUN_INSET_SETTINGS
(for insets other than InsetCollapsables).
3. The parameter to LFUN_INSET_SETTINGS are now not yet implemented (the
parameter like "graphics", "note", "label" and so forth). This causes
the Edit Menu to show all inset-settings variants.
- I don't like checking for this parameter inside the Inset itself (it
should not be dispatched to an inset which is not the target),
- Do you see an opportunity to handle this in the AtPoint mechanism ?
- Do we really need this somewhat "outlandish" parameter ? When used to
choose between the next-inset and underlying inset, it is not failsafe.
When used in the getStatus mechanism, it is only used to determine which
menu item to show, i.e. to have "Note settings.." (is this worth the
trouble) ?
Ideas ?
JMarc
Vincent
