Jean-Marc Lasgouttes wrote:
rgheck <[EMAIL PROTECTED]> writes:
...maybe BufferView is the right place right now. But I still don't
quite understand which dispatch() functions do which things, and what
the chain of control is supposed to be. So if you (or someone) could
explain that, then I think that would help me a lot.
I began to write some things here:
http://wiki.lyx.org/Devel/NotesOnDispatchMechanism
However, I did not get too far, but I'll try to improve on it in the
next days.
Thanks.
I guess what I'm not sure about is how and whether to call
Buffer::dispatch() from LyXView::dispatch() in a kind of "global" way,
or whether to let it happen more on a case-by-case basis, as here.
BufferView::dispatch could preempt the case where the argument is
"custom" and ignore the others. Then Buffer::dispatch would handle the
other cases.
Right. This is starting to make some sense.
I said, I don't feel I understand the architecture well enough to
know. Could Buffer::dispatch() perhaps be called from the default
branch of BufferView::dispatch()??
That would be a possibility. For now I think it is easier to add it to
the default branch of LyXFunc:dispatch, along with the others.
OK. So, let me ask the question I asked in another message: Should I
just add LFUN_BRANCH_ACTIVATE to BufferView::dispatch() for now, and we
can deal with this mess later? With Beta 1 on the horizon, it doesn't
seem like the right time to mess with this part of the code. We could do
this for 1.7, maybe early, and try to clean up the whole dispatch
business then.
rh
