Re: [patch] Up/down cursor in math-macro jumps out of the macro, #3830

[Stefan Schimanski]

Ah yes I remember... I wanted to inverse the logic but never found the time to do so.

So checking for Update::Force is not possible like that. And setting it to NoUpdate first and then check for Force will break a lot I guess.

Right, too late for 1.5. Still the inverse logic is better IMHO.

So it marks the lfun as undispatched. But then the Update::Force flag is overwritten later by the cursor down handler of the text.

Maybe you could change this overwritting?

As far

as I see there is no way to trigger a complete redraw reliable from anywhere else than the inset which dispatches the lfun.

If the Cursor is passed there is: by checking and accumulating the update flag.

What do you mean? I don't see how to do anything like that.

I mean: if (cur.result().update() == Update::Force) this means that the flag has been explicitely set previously as opposed to have the default value (Update::FitCursor | Update::Force). Maybe this information could be used?

Stefan

Tried that and of course there are more problems. Cursor::upDownInMath calls MathMacro::idxUpDown which sets the Update::Force flag. But because it also returns false in the last cell the flags are again restored in upDownInMath, i.e. overwritten once again. It's a mess.

PGP.sig
Description: Signierter Teil der Nachricht