Issue 83399 - Jagged and unsteady lines on screen display
Summary: Jagged and unsteady lines on screen display
Status: CLOSED DUPLICATE of issue 28526
Alias: None
Product: Draw
Classification: Application
Component: viewing (show other issues)
Version: OOo 2.3
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: Armin Le Grand
QA Contact: issues@graphics
Depends on:
Reported: 2007-11-07 08:00 UTC by IngridvdM
Modified: 2008-10-07 19:45 UTC (History)
3 users (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---

example with living shapes (18.90 KB, application/
2007-11-07 09:41 UTC, IngridvdM
no flags Details
screenshot from draw and pdf export (1.48 MB, image/bmp)
2007-11-07 09:45 UTC, IngridvdM
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description IngridvdM 2007-11-07 08:00:52 UTC
When using polygons for more complex curves the lines on screen display often
look jagged and unsteady as if they got some wrong points caused by rounding
errors or similar or as if not the full given resolution from the screen was
used for rendering. Examples are e.g. circle shapes, pie charts, linear
regression curves in charts, free hand curves in draw, a lot of custom shapes,
etc. I'll attach a document containing examples.
Comment 1 IngridvdM 2007-11-07 09:41:50 UTC
Created attachment 49493 [details]
example with living shapes
Comment 2 IngridvdM 2007-11-07 09:45:06 UTC
Created attachment 49495 [details]
screenshot from draw and pdf export
Comment 3 IngridvdM 2007-11-07 10:44:46 UTC
In the attached screenshot I marked the points where you can see wrong pixels.
As comparison I added how Adobe reader displays the PDF export. This is a strong
indication that not the geometry information itself is wrong but instead there
is an error on the way to the screen.
Comment 4 IngridvdM 2007-11-07 10:54:11 UTC
->Armin, you told me that this will probably be solved with the primitives with
aw033. Can you please take care of this issue. Not sure, maybe there is
something more to do in vcl or in the canvas implementations or so? Thanks a lot!
Comment 5 Armin Le Grand 2007-11-07 11:07:48 UTC
AW: Yes and No. For 3.0, we will have the primitives and will be able to support
AntiAliasing (AA) on different systems. Initially, we will probalbly have
Unix/Linux and Solaris. For Windows, support from VCL-Team is needed. Since this
is not clarified (the time constraints for the needed ressources are not
clarified) i cannot promise this for 3.0 (depending on the System), but we are
working on this intensively.
Setting the decision makers on copy, changing to enhancement.
Comment 6 Armin Le Grand 2008-04-29 03:21:26 UTC
AW: Adapting target to primitive move to 3.1.
Comment 7 Armin Le Grand 2008-10-07 11:38:26 UTC
AW: With aw033 and primitives (since DEV300 m30), the basics for this task are
implemented. The missing rest of this task is double to #i28526# to which i will
set this one double.

*** This issue has been marked as a duplicate of 28526 ***
Comment 8 Armin Le Grand 2008-10-07 11:38:55 UTC
AW: Closing.