[
https://issues.apache.org/jira/browse/PIVOT-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Volkert resolved PIVOT-71.
-------------------------------
Resolution: Fixed
Fixed and verified no regression against Sun JRE. With {1f, 1f}, you have to
use CAP_BUTT as well to keep the ends from bleeding over into the gaps, and you
have to turn anti-aliasing off.
> Dash array (focused state) values are incorrect
> -----------------------------------------------
>
> Key: PIVOT-71
> URL: https://issues.apache.org/jira/browse/PIVOT-71
> Project: Pivot
> Issue Type: Bug
> Components: wtk
> Affects Versions: 1.1
> Environment: OpenJDK
> Reporter: Todd Volkert
> Assignee: Todd Volkert
> Priority: Minor
> Fix For: 1.2
>
>
> We've been using {0.0f, 2.0f} as our dash array for the skins that paint a
> dashed line to represent the focused state. These values are incorrect, and
> we got lucky in that Sun's graphics runtime interpreted them the way they
> did. The dash array {0.0f, 2.0f} means "repeatedly draw a dash of length
> 0.0f followed by a gap of 2.0f", which really means "don't draw anything"!
> However, because Sun's runtime interprets a dash of length zero *at a
> non-zero thickness* to yield a pixel hit. This interpretation is not shared
> by other JREs. NOTE, what we were going for was a dash of length 1 followed
> by a gap of length 1, and {1.0f, 1.0f} yields the exact same behavior on the
> Sun JRE as we had before, but it also yields correct behavior in other JREs.
> Thus, we should change all instances of the old dash arrays to the new.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
