Comment #11 on issue 155 by atdi...@gmail.com: If width or height is zero,
the rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
I agree it doesn't sound like a contract change. His comment seemed to
suggest some clients were broken by the change:
Comment #7 on issue 155 by heue...@gmail.com: If width or height is zero,
the rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
No update on this issue in some time, would it be ok for me to apply this
to release-1.3-branch for Milestone-1.3.2?
--
Comment #8 on issue 155 by atdi...@gmail.com: If width or height is zero,
the rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
See allain's comment in r970, at which he reverted r923.
--
Piccolo2D Developers Group:
Comment #10 on issue 155 by heue...@gmail.com: If width or height is zero,
the rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
I wouldn't say that it is a contract change, since the PBounds javadoc
doesn't make any comment on this situation, other than to
Updates:
Status: Accepted
Labels: Milestone-2.0
Comment #5 on issue 155 by allain.lalonde: If width or height is zero, the
rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
This Issue will be resolved in 2.0. No binary incompatible changes are
Comment #2 on issue 155 by allain.lalonde: If width or height is zero, the
rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
Fixed in r923 as an optimization PBounds.add was not doing work when passed
PBounds was
empty.
--
You received this message because
Updates:
Status: Fixed
Comment #3 on issue 155 by allain.lalonde: If width or height is zero, the
rest of bounds are reset.
http://code.google.com/p/piccolo2d/issues/detail?id=155
(No comment was entered for this change.)
--
You received this message because you are listed in the
