[piccolo2d-dev] Re: Issue 203 in piccolo2d: Missing maven profile for Windows x86_64
Comment #11 on issue 203 by atdi...@gmail.com: Missing maven profile for Windows x86_64 http://code.google.com/p/piccolo2d/issues/detail?id=203 Moving issue to Verified per previous comments. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 203 in piccolo2d: Missing maven profile for Windows x86_64
Updates: Status: Verified Comment #10 on issue 203 by atdi...@gmail.com: Missing maven profile for Windows x86_64 http://code.google.com/p/piccolo2d/issues/detail?id=203 Moving issue to Verified per previous comments. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 205 in piccolo2d: Update copyright year in license header to 2011
Updates: Status: Verified Comment #3 on issue 205 by atdi...@gmail.com: Update copyright year in license header to 2011 http://code.google.com/p/piccolo2d/issues/detail?id=205 Verified. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Are we publishing the maven site + reports?
Or do we intend to? Just curious... -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 181 in piccolo2d: PNode.toImage is not centered and can create cropped images for PNodes with non-integral (x,y) bounds
Comment #14 on issue 181 by atdi...@gmail.com: PNode.toImage is not centered and can create cropped images for PNodes with non-integral (x,y) bounds http://code.google.com/p/piccolo2d/issues/detail?id=181 I'm changing my vote and recommending we move this ticket to a future release (2.0) and intend to implement a fully correct solution. Given that there is a workaround for 1.3, I don't want to cause any regression for people that have implemented workarounds that depend on the behavior of 1.3. Especially since the proposed fix here is not a full fix and will still require workaround. Can I get votes on this recommendation? -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 181 in piccolo2d: PNode.toImage is not centered and can create cropped images for PNodes with non-integral (x,y) bounds
Comment #15 on issue 181 by atdi...@gmail.com: PNode.toImage is not centered and can create cropped images for PNodes with non-integral (x,y) bounds http://code.google.com/p/piccolo2d/issues/detail?id=181 I'm changing my vote and recommending we move this ticket to a future release (2.0) and intend to implement a fully correct solution. Given that there is a workaround for 1.3, I don't want to cause any regression for people that have implemented workarounds that depend on the behavior of 1.3. Especially since the proposed fix here is not a full fix and will still require workaround. Can I get votes on this recommendation? -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 154 in piccolo2d: Zoom handler doesn't interact well with PSwing nodes
Comment #5 on issue 154 by atdi...@gmail.com: Zoom handler doesn't interact well with PSwing nodes http://code.google.com/p/piccolo2d/issues/detail?id=154 In the interest of a 1.3.1 release, I propose we move this to 1.4 milestone so we can give time for discussion of previous comment. I'll wait for votes (or absence of votes), and then move to a 1.4. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 154 in piccolo2d: Zoom handler doesn't interact well with PSwing nodes
Comment #6 on issue 154 by atdi...@gmail.com: Zoom handler doesn't interact well with PSwing nodes http://code.google.com/p/piccolo2d/issues/detail?id=154 In the interest of a 1.3.1 release, I propose we move this to 1.4 milestone so we can give time for discussion of previous comment. I'll wait for votes (or absence of votes), and then move to a 1.4. -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 188 in piccolo2d: wrong line width when drawing general shapes under SWT
Updates:
Status: Accepted
Comment #5 on issue 188 by atdi...@gmail.com: wrong line width when drawing
general shapes under SWT
http://code.google.com/p/piccolo2d/issues/detail?id=188
First thing to note is that this issue (pre-fix) only manifest itself for
on Windows (not Mac OSX or Ubuntu).
Second note is that adding 0.5 does not seem to be necessary. Just setting
the line width is sufficient:
public void drawPath(final Path p) {
gc.setLineWidth((int) lineWidth); // no need to + 0.5 here
gc.setTransform(swtTransform);
gc.drawPath(p);
gc.setTransform(null);
}
According to SWT's Javadoc for setLineWidth():
"Note that line width of zero is used as a hint to indicate that the
fastest possible line drawing algorithms should be used. This means that
the output may be different from line width one."
I believe we are getting this effective behavior by not setting lineWidth,
and the correct fix is to set the line width, without adding the 0.5.
Moving out of Fixed state.
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Are we publishing the maven site + reports?
Good question. We were as part of continuous integration builds some time back. I'm not sure those are still running. michael On Mar 20, 2011, at 3:49 PM, atdixon wrote: > Or do we intend to? Just curious... > > -- > Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
