On Wed, Mar 26, 2003 at 08:33:13AM +0000, Angus Leeming wrote: > Great. A quick grep suggests that this is the only thing using it. perhaps > you'd have a go at culling the offending code?
I'd rather tag it and wait for the rest to be ported, *then* remove stuff. > ps ControlChanges is also the main offender requiring kernel().bufferview(). > Perhaps we need a new lfun to dispatch this info to the frontends? What do > you think? > > return lyxfind::findNextChange(kernel().bufferview()); > lyxfind::findNextChange(kernel().bufferview()); > lyxfind::findNextChange(kernel().bufferview()); Sure, these can be LFUNized (and should be). Same goes for ControlSearch. > Change c(kernel().bufferview()->getCurrentChange()); > Change c(kernel().bufferview()->getCurrentChange()); AFAICS this will need to do something similar anyway, the user can place the cursor anywhere etc. john
