Jean-Marc Lasgouttes wrote:
Abdelrazak Younes <you...@lyx.org> writes:
Vincent van Ravesteijn - TNW wrote:
3. Yet another way is to introduce a new LyXAction flag that says that
this lfun should be dispatched both to the current inset as to the next
inset. In that case, we could process the argument in Inset::dispatch.
That would mean AtPointAll (or something like that). (Choosing for this
method would also mean to centralize the handling of LFUN_INSET_SETTINGS
in the Inset class (to avoid duplicating code) and use an improved
editable() mechanism to decide which Inset has a settings dialog (or
introduce the hasInsetDialog() function, but I didn't really get the
opinion of Andre about this. It was hidden somewhere between irony and a
dilemma)).
I hope I made it clear. I think I'll vote for 3.
'3' sounds like a good plan.
I suspect there is something I do not understand about what you both are
heading. And this is bothering me ;) I'd prefer to understand and either
agree or disagree, but I simply do not understand.
AFAICS, we all speak about the same issue but Vincent's solution is to
indicate into the LFUN if there is more than one dispatch() possible;
whereas you prefer to let the inset decide by themselves.
AFAICS, the problem _might_ be related to the following question: assume
that the cursor is the `I' in the nice hand drawing below
|float--------------------------------|
| |box-------------------------------||
| | foo bar I[graphics] ||
| |----------------------------------||
|-------------------------------------|
Current, what is visible (or should be IMO in the Edit menu is)
Graphics settings...
Box Settings...
Float Settings...
Of course, I have a box in a box, then only the inner box will be
accessible this way, and this may be confusing to some people (although
we never had such a complaint). But I think it is useful in most cases.
I would personally appreciate to see the same commands in the context
menus.
Me too.
Abdel.
