My client (PhET) uses PSwing quite heavily. But I'm not going to -1 in order to get the 163 fix, for 3 reasons: (1) The consensus within PhET is that we're comfortable with patching our 1.3 copy to resolve 163. (2) Imho PSwing needs an internal overhaul, to bring the code up to the standards of Piccolo. Poor name choices is my biggest beef, luckily with private stuff. (3) There are additional PSwing issues that need to be resolved. We have not yet reported these, but are tracking them internally. The big 2 issues are focus traversal and memory leaks when PSwings are removed from the scenegraph.
Chris On Feb 26, 4:16 pm, Michael Heuer <heue...@gmail.com> wrote: > Michael Heuer wrote: > > Vote will close at 12:00 GMT Friday 26 February 2010. > > I would like to extend to vote deadline until Monday 01 March 2010 to > allow for feedback on recently fixed issues 163 and 165. > > The current vote would pass as it stands and the fixes for those > issues would not be released until a later version. > > michael -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en