Andre Poenitz <[EMAIL PROTECTED]> writes:
| 5. use buildCursor().dispatch() instead of getLyXText()->dispatch() in
| the default branch of BufferView::Pimpl::dispatch() [That's the fun part
| but should not be that hard]
Well... I have my own plans for distpatch...
My take on this is that we should always enter the "distpatch-tree"
from the same point. IMHO the "master" dispatch should handle the
fanning out.
I am not sure how this will interfere with your work.
Master dispatch to me is LyXView::dispatch... this one should send
down to BufferView::dispatch and further on to LyXText::dispatch or
Inset::dispatch.
Why I want this?
I'd like to have one dispatch exit path, so that some operations could
be done there and not be spread out all over, in particular update and
fitcursor.
| 6. Simplify the structure of InsetText::localDispatch by removing most
| of the special RESULT handling (locking and unlocking is done in the
| GlobalCursor::dispatch). The result should be just a big switch.
And I am trying to get rid of the big switch.
| [7. Try to let InsetText::localDispatch use LyXText::dispatch in almost
| all cases]
We should also rename InsetText::localDispatch to just
InsetText::dispatch
| We can stop after any point without any penalty.
>
| Opinions?
I think it seems sound... BUT we have a lot of small regressions wrt
to cursor placement, undo, C&P... none of these will be fixed with
this work. My take is that we should at least make some effort to fix
some of those regressions before beginning to shift things around
again, and to introduce new regressions.
--
Lgb
