Hi, here is an example on
2025.30690 Windows 10
b = op('/').create('baseCOMP')
cOp = b.create('buttonCOMP')
ui.panes.current.placeOPs([cOp])
As a result - buttonCOMP panel is not working + ‘layout dependency loop detected’ warning.
Best,
Alex
Hi, here is an example on
2025.30690 Windows 10
b = op('/').create('baseCOMP')
cOp = b.create('buttonCOMP')
ui.panes.current.placeOPs([cOp])
As a result - buttonCOMP panel is not working + ‘layout dependency loop detected’ warning.
Best,
Alex
Noticed that triggering panel visibility + forcing cook solves it
For example, this works fine:
b = op('/').create('containerCOMP')
b.openViewer()
cOp = b.create('buttonCOMP')
b.cook(force = True, recurse = True)
b.closeViewer()
ui.panes.current.placeOPs([cOp])
2025.31760
I’ve noticed if even run the following from default project (from /project1/):
cOp = op('/').create('sliderCOMP')
cOp.openViewer()
cOp.cook(force = True, recurse = True)
cOp.closeViewer()
ui.panes.current.placeOPs([cOp])
Result - sliderCOMP panel is not updating on mouse events unless cut+paste sliderCOMP.
Also if you run:
cOp = op('/').create('sliderCOMP')
ui.panes.current.placeOPs([cOp])
The original bug is still - loop dependency error and broken panel.
Best,
Alex
Hi @snaut ,
Thanks for the fix in 32260 - that helps a lot.
Here are leftovers that still brake panels:
#slider handle even not visible:
b = op('/').create('containerCOMP')
cOp = b.create('sliderCOMP')
b.cook(force = True, recurse = True)
ui.panes.current.placeOPs([cOp])
#slider handle visible but not moving
b = op('/').create('containerCOMP')
b.openViewer()
cOp = b.create('sliderCOMP')
b.cook(force = True, recurse = True)
b.closeViewer()
ui.panes.current.placeOPs([cOp])
#created annotate panel will be scaled weiredly
#when draggin corners
c = parent().create('annotateCOMP')
ui.panes.current.placeOPs([c])
Cheers,
Alex
Thanks, we’re looking at those issues with Panels now.
Those 3 examples will be fixed in the next build we post (after 2025.32216+).
Thanks for the report.