Issue 100539 - typing is really slow in print layout with notes
Summary: typing is really slow in print layout with notes
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOO310m7
Hardware: Unknown Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-03-25 12:38 UTC by fmms
Modified: 2017-05-20 11:15 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

document which shows the problem (10.12 KB, application/vnd.oasis.opendocument.text)
2009-03-25 13:19 UTC, fmms
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description fmms 2009-03-25 12:38:33 UTC
I am using the most recent OO version (OOO310m7):
$ rpm -qf /opt/ooo-dev3/program/swriter

Displaying notes works great in weblayout, but in pagelayout it is unusable slow.

See the following example:
This is an example Text

Typing a letter before "is" causes the whole page to rerender. (I see the page
borders repainted on every key press) 

The same problem happens with OOO300m15 (3.0.1).

My system is running openSUSE 11.1 has 1.83GHz and 2048 MB.
Comment 1 fmms 2009-03-25 13:19:01 UTC
Created attachment 61172 [details]
document which shows the problem
Comment 2 max.odendahl 2009-03-25 13:24:52 UTC
I cannot reproduce it with m7 on Mac OS

But I know there are certain documents which force a repaint for every key
press, but this happens also in print layout and is not related to notes
Comment 3 michael.ruess 2009-03-26 16:56:59 UTC
MRU->OD: best to reproduce on Linux (also on Solaris, but not this heavy). Open
the attached document, place cursor before note anchor and type text. You will
notice that the paper limits are repainted very often.
Comment 4 Oliver-Rainer Wittmann 2009-04-03 11:24:55 UTC
I have reproduced the described defect on Linux, Windows and Solaris - on Linux
and Windows even, if I hide the note.

First guess of the root cause is that a certain paint is not included in
appropriate paint via a virtual output device. But this needs to be confirmed.
Comment 5 Marcus 2017-05-20 11:15:58 UTC
Reset assigne to the default "".