On Wed, Oct 29, 2003 at 12:58:13PM +0100, Lars Gullik Bjønnes wrote: > Andre Poenitz <[EMAIL PROTECTED]> writes: > > | On Wed, Oct 29, 2003 at 11:42:47AM +0000, Angus Leeming wrote: > >> Andre Poenitz wrote: > >> > >> > > >> > See attached. > >> > > >> > Still inactive (but 'dispatch to tip' starts to become > >> > functional...) > >> > >> I see that your are using 'buildCursor' within lyxfunc.C, but why do > >> you need 'buildCursor' as well as 'ParIterator::asCursor' It seems > >> like one of them does nothing more than call the other. > > > | That's not final structure. In the end the 'cursor' will just be there > | and only modified, not created every time. Both buildCursor and asCursor > | are hacks. > > > | From the code shown, only the loop that dispatches the Lfun from > | innermost to outermost until something handled it will remain. > > Hmm... this kindo goes againt what I am working on.
I thought we already agreed that it isn't as I am working only on what happens below the main text (i.e. the inset hierarchiy) and you are working on the LyXView/LyXFunc/BV interaction. That I currently have a few lines in LyXFunc is just to get started. In the end it is completely irrelevant who calls Cursor::dispatch. > But that should be possible to resolve. > > It seems that we will need two "ways" into the dispatch machinery: > > 1. through the cursor > 2. through the lyxview (lyxfunc) > > (or we could make it so that the lyxview dispatch only is used if no > documents are loaded, so that as long we have a cursor we use that for > dispatch.) Something like that. > One thing that I'l like to do is to make the result of a Dispatch only > have to values: DISPATCHED and UNDISPATCHED. Fine with me. And feasible as the other stuff is handled within the cursor machinery.. > In addition to these I want to add a status field. This will be a > "binary enum" with values such as UPDATE,POP,FINISH_LEFT,FINISH_RIGHT > etc. Fine. Go for it if you wish. > And I want these status to be handled in one place, f.ex. so that if > UPDATE is set we only update once. They will be handled in Cursor::dispatch and the update call is at the end of this. Andre'
