I think I've nailed it down now - the problem is that the clip's treeVisible-Property is not update appropiately, hence it is never taken into account and synced because the system thinks it is invisible after the first initialization.
Tom On 05.08.13 15:26, Tom Schindl wrote: > https://javafx-jira.kenai.com/browse/RT-32123 > > Tom > > On 05.08.13 15:07, Pavel Safrata wrote: >> Hi Tom, >> this is definitely a bug, clip node has to be synced automatically. >> Would you please file a Jira issue? >> Thanks, >> Pavel >> >> On 5.8.2013 13:55, Tom Schindl wrote: >>> Hi, >>> >>> I've been hunting a bug in TitledPaneSkin [1] which makes me wonder if >>> maybe the control code is using the Clip-Feature in appropriately. >>> >>> The code in general looks like this: >>> >>> public class BlaSkin extends Node { >>> private Rectangle rect; >>> >>> public BlaSki() { >>> rect = new Rectangle(); >>> setClip(rect); >>> } >>> >>> public void changeSize(double x, double y) { >>> rect.setWidth(x); >>> rect.setHeight(y); >>> } >>> } >>> >>> so the clipping node changes its size while the code is running but it >>> looks like the rendering code does not know about this and never updates >>> the peer's clipNode (in impl_updatePeer) now I guess this is simply an >>> optimization introduced in FX8 so my question is is Node expected to >>> detect its clip node changes or is the developer forced to somehow tell >>> the Node to do so (my first direct work around was to set the clip to >>> null and back to the rectangle which fixes the problem)? >>> >>> Tom >>> >>> [1]https://javafx-jira.kenai.com/browse/RT-32117 >> >
