Andre Poenitz wrote: >> What's the current_ slice? I thought that the cursor (blinking >> thing) was always the top-most slice. > > We are dispatching to the innermost inset willing to handle an LFUN. > This means going down the slice stack. Of course we can't just pop > slices while trying to dispatch as the handling inset might just > want to pop up a dialog but not move the cursor tip at all. > 'current_' is the 'interesting' slice in then stack. Therefore, an > inset's dispatch just needs to access 'cur.pos()' to get the cursor > position in the slice it is supposed to look at (which is not > necessarily the cursor tip)
Thank you for the explanation. >> Do you have any plans to address the nastiness in LCursor::getPos? > > Well, I don't intend to enter all math at position (100,100), so > this should be obvious. Actually, I meant the outer world stuff that has the long explanation. > So you basically have a choice of a 270k buggy patch applied and > waiting for an even larger one. Do whatever is easiest for you. Note that Alfredo is pretty good at tracking down off by one errors. (You've already warned people not to use current cvs for real work.) -- Angus
