Issue 20368 - Q-PCD Performance-5: repaint speed
Summary: Q-PCD Performance-5: repaint speed
Status: CLOSED DUPLICATE of issue 20249
Alias: None
Product: gsl
Classification: Code
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: Other Other OS
: P3 Trivial (vote)
Target Milestone: OOo 2.0
Assignee: christof.pintaske
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-29 18:27 UTC by christof.pintaske
Modified: 2005-01-25 15:52 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description christof.pintaske 2003-09-29 18:27:04 UTC 
Category
Drawing Refresh

Product Requirement 
Content on document window disappears, makes the application look like it is
buggy and has poor performance. May be related to drawing/refresh speed, time it
takes to draw or refresh graphical displays. Especially on Solaris.

Customer Need/Problem
Application should not loose visual display of data/information on document
window while users is working. Is this is a known bug in 6.0 related to refresh
speed? it makes the application look buggy.
Comment 1 christof.pintaske 2003-09-29 18:27:37 UTC 
change component to gsl
Comment 2 lutz.hoeger 2003-10-23 07:45:09 UTC 
added keyword Q-PCD
Comment 3 christof.pintaske 2004-08-18 15:04:40 UTC 
this is not an issue with the repaint speed but with redraw while scrolling.  in
OOo 1.x tooltip windows left traces when scrolling under them. To reproduce
create a multipage text document, resize it in a way that the text goes up to
right application border and scroll up and down. Windows with changing page
numbers pop up and down. They should not leave any "dirt" on the document window.

This is already better by magnitudes in 8, we need to verify if there is
anything left.

As discussed with DL I set this to "bug" as it is definitively one.
Comment 4 christof.pintaske 2005-01-25 15:50:54 UTC 
we fixed the initial problem with i20249. No need to keep this open any longer.
If we experience more problems we will write dedicated bugs for them. 

*** This issue has been marked as a duplicate of 20249 ***
Comment 5 christof.pintaske 2005-01-25 15:52:54 UTC 
closing