[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Updates: Status: Accepted Labels: Milestone-3.0 Comment #8 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Updates: Owner: heue...@gmail.com Comment #9 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Updates: Status: Started Comment #10 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 $ svn commit -m Issue 166 ; refactor PNode moveToBack and related . Sendingcore/src/main/java/org/piccolo2d/PNode.java Sendingcore/src/main/java/org/piccolo2d/event/PDragEventHandler.java Sendingcore/src/test/java/org/piccolo2d/PNodeTest.java Sending core/src/test/java/org/piccolo2d/event/PDragEventHandlerTest.java Sending examples/src/main/java/org/piccolo2d/examples/GridExample.java Sending examples/src/main/java/org/piccolo2d/tutorial/PiccoloPresentation.java Transmitting file data .. Committed revision 1227. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Comment #11 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 $ svn commit -m Issue 166 ; mark PNode moveToFront and related as @deprecated . Sendingcore/src/main/java/org/piccolo2d/PNode.java Sendingcore/src/main/java/org/piccolo2d/event/PDragEventHandler.java Transmitting file data .. Committed revision 1228. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Updates: Status: Fixed Comment #12 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 (No comment was entered for this change.) -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en --- You received this message because you are subscribed to the Google Groups Piccolo2D Developers group. To unsubscribe from this group and stop receiving emails from it, send an email to piccolo2d-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Comment #5 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 Copying this comment from a thread on piccolo2d-dev@ to here cmal...@pixelzoom.com wrote: I realize this is z-ordering. But if this is supposed to replace the existing z-ordering interface, then raise and lower would be replacing moveToFrontOf(PNode) and moveInBackOf(PNode). So, again, how does raise and lower allow me to put one sibling in front/back of another sibling? Imho, this new interface proposal reduces the functionality of the interface, and (as Allain noted previously) makes make changing the z-order of siblings cumbersome, if not downright difficult. -- 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 166 in piccolo2d: Refactor PNode.moveToBack() and related
Comment #6 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 Methods that change the Z-order of a peer node void raiseAbove(PNode peer) void lowerBelow(PNode peer) ? -- 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 166 in piccolo2d: Refactor PNode.moveToBack() and related
I realize this is z-ordering. But if this is supposed to replace the existing z-ordering interface, then raise and lower would be replacing moveToFrontOf(PNode) and moveInBackOf(PNode). So, again, how does raise and lower allow me to put one sibling in front/back of another sibling? Imho, this new interface proposal reduces the functionality of the interface, and (as Allain noted previously) makes make changing the z-order of siblings cumbersome, if not downright difficult. Chris On Feb 27, 1:00 pm, Samuel Robert Reid re...@colorado.edu wrote: raise and lower relative to what? This is regarding the z-ordering of child nodes within a parent node. Sam Reid -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
Re: [piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
raise and lower relative to what? This is regarding the z-ordering of child nodes within a parent node. Sam Reid -- Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
[piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related
Updates: Labels: Milestone-2.0 Type-Enhancement Priority-Low OpSys-All Effort-Low Toolkit-Piccolo2D.Java Component-Core Usability Comment #1 on issue 166 by allain.lalonde: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 Unless you keep the existing methods doesn't moving a child to be immediately before one of its siblings cumbersome? -- 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 166 in piccolo2d: Refactor PNode.moveToBack() and related
Updates: Status: Accepted Comment #3 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack() and related http://code.google.com/p/piccolo2d/issues/detail?id=166 False alarm, issue 165 was fixed by r974, not this one. -- 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