Comment #9 on issue 164 by allain.lalonde: PNode#moveToFront change to
avoid java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
agreed
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Comment #8 on issue 164 by heue...@gmail.com: PNode#moveToFront change to
avoid java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
OK if we mark as WontFix then?
--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Updates:
Owner: allain.lalonde
Comment #5 on issue 164 by allain.lalonde: PNode#moveToFront change to
avoid java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
Should I modify getChildrenReference to user Collections.unmodifiableList ?
Comment #6 on issue 164 by samrreid: PNode#moveToFront change to avoid
java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
Immutability would be safest, but since the method is named
getChildrenReference, it
is possible that some client code is
Comment #7 on issue 164 by allain.lalonde: PNode#moveToFront change to
avoid java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
Agreed that if a client is directly manipulating the reference, their code
will
break, but since getChildReference
Comment #2 on issue 164 by heue...@gmail.com: PNode#moveToFront change to
avoid java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
See also Issue 166.
--
You received this message because you are listed in the owner
or CC fields of this issue,
Comment #4 on issue 164 by mr0...@mro.name: PNode#moveToFront change to
avoid java.util.ConcurrentModificationException
http://code.google.com/p/piccolo2d/issues/detail?id=164
immutable? love this idea.
--
You received this message because you are listed in the owner
or CC fields of this
