[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-08-24 Thread piccolo2d


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


[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-08-23 Thread piccolo2d


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


[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-04-17 Thread piccolo2d

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 ?

--
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


[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-04-17 Thread piccolo2d


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 relying on the ability to directly  
manipulate
the list of children.  Therefore, it could be confusing to have this return  
a

defensive list copy.

--
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


[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-04-17 Thread piccolo2d


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 is documented explicitly as do not  
touch, I

think that's ok.



--
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


[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-04-09 Thread piccolo2d


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, 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

To unsubscribe, reply using remove me as the subject.


[piccolo2d-dev] Re: Issue 164 in piccolo2d: PNode#moveToFront change to avoid java.util.ConcurrentModificationException

2010-04-09 Thread piccolo2d


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 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

To unsubscribe, reply using remove me as the subject.