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. > Apart from that, it seems to make sense, although it'll be fun to see > (perhaps dummy) handlers for the LFUN in the insets. ? Which LFUN? [And note that inserting chars and other simple operations already work if the facility is activated] Andre' -- Those who desire to give up Freedom in order to gain Security, will not have, nor do they deserve, either one. (T. Jefferson or B. Franklin or both...)
