Stefan Schimanski wrote:
No, it's not intentional. It's a bug that notifyCursorLeaves is not
called. Had noticed that before some time ago. Will look into it.
This whole updateflag business makes me crazy. The MathMacro get's the
notifyCursorLeaves call. It then sets the Update::Force flag to trigger
a redraw. But of course the MathMacro does not know what should happen
on cursorDown from the last cell.
Couldn't it check if the flag is set to Update::Force?
So it marks the lfun as undispatched.
But then the Update::Force flag is overwritten later by the cursor down
handler of the text. 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.
Abdel.