PixiJS Layout version
3.2.0
PixiJS version
8.14.3
Link to minimal reproduction
https://stackblitz.com/edit/pixijs-layout-vgadp3py?file=src%2Fmain.js
Steps to reproduce
-the scene and bug case is already setup at stackblitz.
-check the logs.
-some layout values will be shown incorrect even if they true in layout object.
What is expected?
the values like "realWorldX" and "computedPixiLayout.x" should be different than 0.
It should report the correct value which is written in layout object.
What is actually happening?
"realWorldX" and "computedPixiLayout.x" and other related values return 0 at first initialize.
calling "forceUpdate()" on all layouts doesn't affect it.
after first frame, -inside update calls- the correct values return.
strange part, if you print layout directly, the values are shown correct at even start-up.
for example, inside layout objects computedPixiLayout.x value is "192"
but if you print "computedPixiLayout.x" directly, it shown up as "0"
Environment
-seems Not browser related. It occurs on Chrome and Edge
-seems not OS related. Tested on Windows 11
Any additional comments?
If you create an object after the game start, the bug occurs again. I think it is not related the pixi.js start-up.
PixiJS Layout version
3.2.0
PixiJS version
8.14.3
Link to minimal reproduction
https://stackblitz.com/edit/pixijs-layout-vgadp3py?file=src%2Fmain.js
Steps to reproduce
-the scene and bug case is already setup at stackblitz.
-check the logs.
-some layout values will be shown incorrect even if they true in layout object.
What is expected?
the values like "realWorldX" and "computedPixiLayout.x" should be different than 0.
It should report the correct value which is written in layout object.
What is actually happening?
"realWorldX" and "computedPixiLayout.x" and other related values return 0 at first initialize.
calling "forceUpdate()" on all layouts doesn't affect it.
after first frame, -inside update calls- the correct values return.
strange part, if you print layout directly, the values are shown correct at even start-up.
for example, inside layout objects computedPixiLayout.x value is "192"
but if you print "computedPixiLayout.x" directly, it shown up as "0"
Environment
-seems Not browser related. It occurs on Chrome and Edge
-seems not OS related. Tested on Windows 11
Any additional comments?
If you create an object after the game start, the bug occurs again. I think it is not related the pixi.js start-up.