Issue 121549 - Negative angles in command U are treated as zero
Summary: Negative angles in command U are treated as zero
Status: UNCONFIRMED
Alias: None
Product: Draw
Classification: Application
Component: code (show other issues)
Version: 4.0.0-dev
Hardware: PC Windows XP
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-27 14:46 UTC by Regina Henschel
Modified: 2012-12-27 14:46 UTC (History)
2 users (show)

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

Attachments
File containing custom shapes with U commands (11.84 KB, application/vnd.oasis.opendocument.presentation)
2012-12-27 14:46 UTC, Regina Henschel 		no flags Details
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 Regina Henschel 2012-12-27 14:46:23 UTC 
Created attachment 80071 [details]
File containing custom shapes with U commands

When a custom shape is defined by a U command with negative angle, this angle is treated as zero. This should not happen, because there is no such constraint in the spec for this angles.

The predefined custom shapes, which use the U command, use always angle 0° to 360°, so the error was undetected up to now.

The attached document contains some custom shapes with U command. Their angle values increase and decrease with 90 degrees. The used range is noted in the text of the shape. The angles have fixed values because of the problem with handles and with orientation in bug 121491.

BTW:
I have looked into createPolygonFromUnitEllipseSegment in basegfx\source\polygon\b2dpolygontools.cxx in the context of this bug. I do not understand, why the angles are trimmed there at all. That forces all callers to workaround the angle range restriction.