On Sun, Mar 20, 2005 at 01:48:08PM +0100, Alfredo Braunstein wrote:
> Juergen Spitzmueller wrote:
>
> > Martin Vermeer wrote:
> >> I think I know where the problem is, not how to fix it :-(
> >
> > Me too. It seems that MOUSE_MOTION moves inside nested insets despite of
> >
> > // only accept motions to places not deeper nested than the real anchor
> > if (bvcur.anchor_.hasPart(cur)) {
> >
> > No idea why.
>
> Nice spot. I had a look.
>
> The problem is the following: the MOTION event is indeed ignored in the
> inner table, but when it is handled in the outer one InsetTabular::setPos
> is called to positionate the cursor in the right cell, but setPos wrongly
> descends into insets.
>
> I attach a tentative solution (make setPos not descend), tested only
> once ;-). Feedback greatly appreciated.
>
> AlfredoYes, this seems to work consistently for me. Onward to the next bug... - Martin
pgpnokqSiXrJE.pgp
Description: PGP signature
