generic 24.04 writer performance ticket about online HOT 6 OPEN

24.04 writer profile where we endured a slowdown after (possibly) selecting all text in 72 page and changing the font size.

Showing a cursor seems to have found some case where the notorious solveCrossovers gets called, odd

from online.

Showing a cursor seems to have found some case where the notorious solveCrossovers gets called, odd

That means that we have a selection overlay which (a) consists or more than one rectangle and (b) has a border, in which case we try and convert it into a "nicer" overlay polygon with a single continuous border.

Possibly we should just do what other software does and have multiple rectangles for that case, even if it means the borders don't look quite as nice.

Or maybe get alg to write us an optimised variant of that solveCrossovers() which only handles combining rectangles?

from online.

Or maybe get alg to write us an optimised variant of that solveCrossovers() which only handles combining rectangles?

Some interesting suggestions here, for such an algorithm: https://stackoverflow.com/questions/13746284/merging-multiple-adjacent-rectangles-into-one-polygon

from online.

The curious thing is that we split that polygon per-page; I wonder if by pushing that knowledge from up the stack down to here we could save trying to do 72 pages worth of pointless intersection, and just do that a page at a time (?) =) or perhaps we already do that (?)

from online.

No, it doesn't look like we pass down the selection as per-page information, it's just one big vector of rectangles.

Anyhow, WIP attempt at speeding this up at https://gerrit.libreoffice.org/c/core/+/165752

from online.

Today's typical small meeting document

from online.