Issue 49141

Summary:

Fat lines appear fragmented in Direct-X view

Product:

Impress

Reporter:

lutz.hoeger

Component:

viewing

Assignee:

AOO issues mailing list <issues>

Status:

ACCEPTED ---

QA Contact:

Severity:

Trivial

Priority:

CC:

issues

Version:

680m102

Target Milestone:

---

Hardware:

All

OS:

Windows, all

Issue Type:

DEFECT

Latest Confirmation in:

---

Developer Difficulty:

---

Attachments:

Description	Flags
fat line fragmented in direct-x view (preso)	none
screen shot of fragmented fat line in direct-x view taken on my system	none
Faint lines even without thick lines	none

Description lutz.hoeger 2005-05-12 12:51:32 UTC

see attached screen shot and preso; in presentation mode using direct-x there
are tiny white spaces between the polygon segments, which make the line appear
fragemented. Even without the white spaces the polygon pieces look "gestÃ¼ckelt"
- can't we achieve a smoother line appearance?

Comment 1 lutz.hoeger 2005-05-12 12:54:03 UTC

Created attachment 26051 [details]
fat line fragmented in direct-x view (preso)

Comment 2 lutz.hoeger 2005-05-12 12:54:49 UTC

Created attachment 26052 [details]
screen shot of fragmented fat line in direct-x view taken on my system

Comment 3 thb 2005-05-12 13:00:52 UTC

This bug has several aspects. First of all, the problem seems to be
machine/resolution/screen depth dependent: on my box, it only appears in 16 bit,
for LHO, it's on all depths, for AW and DL, it happens for _no_ case.

Then, it's certainly possible to 'tunnel' the high-level line information down
to the canvas. This would fix the problem, but leave the general one, namely,
that exactly adjacent polygons are seemingly not always rendered exactly
adjacent (see attached document).

Maybe it's even caused by round-off errors above the renderer (->cppcanvas).

Comment 4 thb 2005-05-12 13:04:19 UTC

Created attachment 26054 [details]
Faint lines even without thick lines

Comment 5 thb 2005-05-27 23:45:24 UTC

Retargeted, due to resource constraints.

Comment 6 thb 2012-07-13 20:47:36 UTC

Reset to default bug assignee.