On Sun, Feb 01, 2004 at 01:08:37PM +0100, Alfredo Braunstein wrote: > the problem seems to consist in the following: > > - the click is dispatched through a temporary cursor cur to which this > collapsable's CUrsorSlice is pushed (the real cursor is still elsewhere); > so
Yes. That's to raise the possibility of _not_ interpreting the click as cursor positioning (but, e.g. as 'pop up some menu') > - insetcollapsable::edit takes this cur argument; then > > - insettext::edit also takes this cur argument, but it calls > > - lyxtext::setCursor without the cur argument > > and LyXText::setCursor tries in vain to find itself in the *real* cursor > (using LyxText::cursor, and ::findText(LyXText *) both of which use the > real cursor). Ahja. > (btw, why is that ::findText needed at all, didn't we agree that the > current() slice is what is needed there? IMO for debugging wouldn't be > enough to assert on current().text() == text) Sort of leftover from the transition. We should use the assert. > André, can you have a look? Later today. 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...)
