Comment #5 on issue 161 by allain.lalonde: full bounds behavior has changed
in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
We've tried as much as possible to cause no breaking changes while fixing
bugs,
but... the fix to Issue 155 has obviously done so.
With
Comment #6 on issue 161 by re...@colorado.edu: full bounds behavior has
changed in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
I agree with the recommendation in Comment 5 to roll back the fix for issue
155 for
the 1.3 release. Should we plan on a 1.3rc3 for this?
Comment #7 on issue 161 by allain.lalonde: full bounds behavior has changed
in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
Regarding comment 4... I'd be OK with that approach, but I think that it
ought to be
the exception rather than the rule. Children classes who
Revision: 970
Author: allain.lalonde
Date: Tue Feb 9 07:58:01 2010
Log: Reverting r923 since it was a breaking change. It will need to be
redone in 2.0. Seems that some apps were making use of this behaviour.
http://code.google.com/p/piccolo2d/source/detail?r=970
Modified:
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 #9 on issue 161 by heue...@gmail.com: full bounds behavior has
changed in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
Any of us can change our votes on 1.3-rc2 if necessary.
--
You received this message because you are listed in the owner
or CC fields of this
Comment #10 on issue 161 by cmal...@pixelzoom.com: full bounds behavior has
changed in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
Btw... Just for the record, we've found a second PhET application broken by
this
change. And there are probably others that we haven't
Comment #11 on issue 161 by allain.lalonde: full bounds behavior has
changed in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
I've reverted and re-opened.
Regarding the rc, technically yes we should re-vote.
Since this is the only change, if things run off the trunk,
I'm re-voting, based on our discussion in issue 161.
---
[ ] +1 I support this release
[ ] +0
[ ] -0
[ X] -1 I oppose this release because (as described in issue 161)
full bounds behavior was changed by fixing issue 155.
--
Piccolo2D Developers Group:
Comment #13 on issue 161 by heue...@gmail.com: full bounds behavior has
changed in Piccolo 1.3
http://code.google.com/p/piccolo2d/issues/detail?id=161
I don't mind putting out new RCs, it's better late than never.
Binding votes are those from project committers.
Non-binding votes are those
Comment #1 on issue 162 by re...@colorado.edu: Improve semantics for full
bounds computation
http://code.google.com/p/piccolo2d/issues/detail?id=162
Allain said [in comment 7 of issue 161]:
Regarding [the above proposal]... I'd be OK with that approach, but I think
that it
ought to be
11 matches
Mail list logo
