(incubating) | The Free and Open Productivity Suite
Announcing Apache OpenOffice 3.4

Developer's Guide

API

SDK

Tips 'n' Tricks

Miscellaneous

Content for OpenOffice.org version 3.3.

:: com :: sun :: star :: rendering ::

unpublished constants group PathJoinType
Usage Restrictions
not published
Description
Determines which shape to use when joining path segments.

The joins between different paths segments can be formed out of several different shapes (which are of course only visible for strokes wider than one device pixel).

Since
OOo 2.0.0

Constants
NONE Do not join the path segments at all. 
MITER Join the path segment by extending the outer border until they intersect.  
ROUND Join the path segment with a pie-like patch, such that the outer line of the meeting point is round.  
BEVEL Join the path segment by connecting the outer ends of the abutting segments with a straight line.  
Constants' Details
NONE
const byte NONE =0;
Description
Do not join the path segments at all.

This join type might lead, depending on the angle between the segments, to visible cracks at the meeting points.

MITER
const byte MITER =1;
Description
Join the path segment by extending the outer border until they intersect.
ROUND
const byte ROUND =2;
Description
Join the path segment with a pie-like patch, such that the outer line of the meeting point is round.
BEVEL
const byte BEVEL =3;
Description
Join the path segment by connecting the outer ends of the abutting segments with a straight line.
Top of Page

Apache Feather

Copyright & License | Privacy | Contact Us

Apache and the Apache feather logos are trademarks of The Apache Software Foundation. OpenOffice.org and the seagull logo are registered trademarks of The Apache Software Foundation. Other names appearing on the site may be trademarks of their respective owners.

Apache OpenOffice is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Apache Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.