Bug 505979 - Fontwork slow to display
Fontwork slow to display
Status: CLOSED UPSTREAM
Product: Fedora
Classification: Fedora
Component: openoffice.org (Show other bugs)
11
All Linux
low Severity low
: ---
: ---
Assigned To: Caolan McNamara
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-06-14 22:52 EDT by Steven Drinnan
Modified: 2009-06-15 06:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-06-15 06:55:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
OpenOffice.org 100851 None None None Never
OpenOffice.org 100929 None None None Never

  None (edit)
Description Steven Drinnan 2009-06-14 22:52:53 EDT
Description of problem:

When you open or insert fontwork the document becomes very slow.
This was not present in F10


Version-Release number of selected component (if applicable):
3.1.0

How reproducible:
Allways - just open a document with fontwork

Steps to Reproduce:
1.Open openoffice
2.Select a new document
3. Add fontwork
  
Actual results:

Very slow, screen takes a long time to refresh


Expected results:

Displays and refresh is much faster, like it was in 3.0v



Additional info:
Comment 1 Caolan McNamara 2009-06-15 06:52:58 EDT
Seem's alright to me, probably routed from the changes to fontwork for 3.1, i.e. ironically http://qa.openoffice.org/issues/show_bug.cgi?id=100851

Turning off Tools->options->antialiasing might make a difference to you
Comment 2 Caolan McNamara 2009-06-15 06:55:31 EDT
http://qa.openoffice.org/issues/show_bug.cgi?id=100929 for 3.2 will improve this a bit, but the fundamental change is almost certainly that AA is on by default in 3.1, which is the change versus 3.0. On my own particular card

Note You need to log in before you can comment on or make changes to this bug.