Closed
Bug 2150
Opened 26 years ago
Closed 25 years ago
GFX coordinate problems, pixel compatability between platforms
Categories
(Core Graveyard :: GFX, defect, P1)
Tracking
(Not tracked)
VERIFIED
FIXED
M17
People
(Reporter: sdagley, Assigned: waqar)
References
Details
(Keywords: platform-parity)
Due to differing coordinate systems/pen hang items drawn with specific pixel
positioned vertices don't draw the same on different platforms
NOTE - this bug is supposed to be cc:'ed to saari@netscape.com but he apparently
doesn't have a Bugzilla account.
Updated•26 years ago
|
Severity: normal → major
Comment 2•26 years ago
|
||
how much work is involved in fixing this?
a) finding out where each platform defines a pixel center to be.
b) per api *where pixel identity can be defined reasonably in an xp fashion*,
finding out where each platform expects vertices to be.
c) based on information from a and b, defining in an xp way how gfx expects
these to behave.
d) making each platform compliant.
e) fixing all of the places that break as a result of the changes.
Updated•26 years ago
|
QA Contact: 2792
Comment 6•26 years ago
|
||
setting Eli as QA contact for this bug, to track and review
Updated•26 years ago
|
QA Contact: 2792 → 4130
Comment 7•26 years ago
|
||
assigned to incorrect qa -- reassigning to Claudius
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
Assignee: michaelp → kmcclusk
Status: ASSIGNED → NEW
Target Milestone: M4 → M5
kevin, the pixel coverage has been defined, we just need to make all of the
platforms compliant. give me a call and i can pass on the relevant info. x3178.
Updated•26 years ago
|
Target Milestone: M5 → M6
Updated•26 years ago
|
Status: NEW → ASSIGNED
Updated•26 years ago
|
Target Milestone: M6 → M7
Updated•26 years ago
|
Target Milestone: M7 → M8
Updated•26 years ago
|
Target Milestone: M8 → M9
Comment 10•26 years ago
|
||
Moving to M9
Comment 11•26 years ago
|
||
Ramiro, do we have a document that describes what the policy for pixel coverage
is?
Updated•26 years ago
|
Target Milestone: M9 → M10
Comment 12•26 years ago
|
||
Moving to M10. This is next on my list after the M9 bugs.
Comment 13•26 years ago
|
||
Talked to Michael P. to clarify. He will be forwarding a email discussion which
defines the pixel coverage to me. From the phone conversation:
drawing a line should not cover the ending pixel.
All rendering context calls which take a rect precisely define the pixel
coverage through the width and height. All platforms need to honor this.
WIN32's varies between fillrect and drawrect.
Updated•26 years ago
|
Target Milestone: M10 → M11
Comment 14•26 years ago
|
||
Moving to M11
Comment 15•25 years ago
|
||
Created a simple cross platform, pixel coverage test app so we can identify
which platforms are not rendering lines and rectangles as expected. It
is located in mozilla/gfx/tests/coverage.
Updated•25 years ago
|
Assignee: kmcclusk → dcone
Status: ASSIGNED → NEW
Comment 16•25 years ago
|
||
Don, I'm reassigning this to you. Please run the gfx pixel coverage test. Once
the coverage is correct on the Mac. Reassign to Ramiro to check Linux.
Updated•25 years ago
|
Assignee: dcone → ramiro
Comment 17•25 years ago
|
||
Got the Mac version working and added. Ramiro can you check Linux.
Updated•25 years ago
|
Assignee: ramiro → waqar
Comment 18•25 years ago
|
||
reassign to waqar.
waqar: this is a pretty simple thing to fix. just make sure the test app runs.
i think there were some issues with test apps on linux. pavlov can help you.
Assignee | ||
Comment 19•25 years ago
|
||
Mass move to M15
Updated•25 years ago
|
Summary: [PP] GFX coordinate problems, pixel compatability between platforms → GFX coordinate problems, pixel compatability between platforms
Comment 21•25 years ago
|
||
This is fixed, all platforms have this adjustment. I did the final adjustment
on Linux and Mac has this fix.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → FIXED
Updated•16 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•