Comment #8 on issue 161 by [email protected]: full bounds behavior has
changed in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
I also agree with Allain's recommendation to roll back the fix for issue
155, and
reopen that ticket. Keeping the behavior the same in a point release is
the first
priority, no matter what we think about what might be "better" behavior.
Changing the behavior is more appropriate to address in 2.0. So regarding
Sam's
proposal in comment 4... I would need to think about it some more, and I
think the
idea may need some refinement. So yes, a new ticket to track that as a
feature
proposal and it's possible inclusion in 2.0.
Finally... Do we need to fail 1.3-rc2 because of this? Technically, I
think so.
I've already voted to support the release, but Sam has not voted.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
