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
Updates:
Status: Fixed
Comment #2 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack()
and related
http://code.google.com/p/piccolo2d/issues/detail?id=166
This issue was closed by revision r974.
--
You received this message because you are listed in the owner
or CC fields o
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 o
Comment #4 on issue 166 by cmal...@pixelzoom.com: Refactor
PNode.moveToBack() and related
http://code.google.com/p/piccolo2d/issues/detail?id=166
raiseToTop() == moveToFront()
lowerToBack() == moveToBack()
But I don't understand how the 4 raise and lower methods work -- raise and
lower
rel
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 n
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
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 ar
Updates:
Status: New
Labels: -Milestone-2.0
Comment #7 on issue 166 by heue...@gmail.com: Refactor PNode.moveToBack()
and related
http://code.google.com/p/piccolo2d/issues/detail?id=166
My revised proposal is as follows:
Methods that change the Z-order of this
void raise();
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 pr
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
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
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
Sendin
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
> 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
14 matches
Mail list logo