Recently, I have observed strange behaviors in the auto positioning feature. It could be a possible bug.
First, when the x and y coordinates are set to -1, after they are positioning into grid their coordinates still remain -1 until they are moved or re-sized. Then, they get their correct positions. Wouldn't be nice if they are set to their correct positions as soon as they are added to the grid?
Second, adding an auto positioning child to the grid causes a change in coordinates of other components (both axes and sizes). The effect is not observed in the UI (JS coordinates remain correct), however server side coordinates become completely different from the UI. I have produced this with the following steps and changes in the DemoUI.
1) Initially, grid contains one "console" component added as [-1,-1 4,2].
2)Add one "Hep" component again as [-1,-1, 1,1] and console component changes as [4,0 1,1].
3)Resize (vertically) "Hep" component and all coordinates get corrected as [0,0 4,2] and [4,0 1,2].
4)Add another auto positioning "Hep" component and all coordinates changes again as [4,0 1,2], [5,0 1,2] and [-1,-1 1,1].
Could you reproduce the issue? If so, do you have any suggestion what might be wrong? I am also looking into this.
Recently, I have observed strange behaviors in the auto positioning feature. It could be a possible bug.
First, when the x and y coordinates are set to -1, after they are positioning into grid their coordinates still remain -1 until they are moved or re-sized. Then, they get their correct positions. Wouldn't be nice if they are set to their correct positions as soon as they are added to the grid?
Second, adding an auto positioning child to the grid causes a change in coordinates of other components (both axes and sizes). The effect is not observed in the UI (JS coordinates remain correct), however server side coordinates become completely different from the UI. I have produced this with the following steps and changes in the DemoUI.
1) Initially, grid contains one "console" component added as [-1,-1 4,2].
2)Add one "Hep" component again as [-1,-1, 1,1] and console component changes as [4,0 1,1].
3)Resize (vertically) "Hep" component and all coordinates get corrected as [0,0 4,2] and [4,0 1,2].
4)Add another auto positioning "Hep" component and all coordinates changes again as [4,0 1,2], [5,0 1,2] and [-1,-1 1,1].
Could you reproduce the issue? If so, do you have any suggestion what might be wrong? I am also looking into this.
Thanks, -K