Comment #4 on issue 161 by re...@colorado.edu: full bounds behavior has
changed in Piccolo 1.3
Here's a proposed behavior that I think is predominantly consistent with
behavior, and that makes more sense to me.
1. Container PNodes (i.e. nodes that have children but do not define any
themselves) should have PBounds[EMPTY] and not be taken into consideration
2. Content PNodes (i.e. PPath, PText or other nodes that define their own
may additionally have children) should never have PBounds[EMPTY] and should
taken into consideration when computing FullBounds. This means that
PPath(Rectangle(0,0,0,0)) would have PBounds(0,0,0,0) and would impact
if it is not displayed on the screen under any zoom parameters. Similarly
PText(""), an empty PImage etc.
This seems like it would provide reasonable and reliable behavior for
layouts. This would also make the graphical output in DebugFullBounds.java
and its readout of PBounds[EMPTY] for 0-width 0-height rectangles
behavior is also consistent with the desired behavior reported in Issue 155.
If we agree that this is the best semantics for layout, then we will next
discuss the best way of implementing this behavior.
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:
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en