You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When inserting a new Pane into Tiles, it returns a new TileId. The behavior I'd expect is for this TileId to consistently refer to the same Pane throughout the lifetime of the Tree.
However, this seems this is not the case; when a e.g. Tabs container with two Panes is changed into a HorizontalContainer, my first Pane's TileId refers to the HoritonzalContainer in which the Pane's TileId is stored.
Would it be possible to keep current TileIds always refer to the same Tile? Not only would this remove the need to manually keep track of which CustomId belongs to which Pane, it would also fit (atleast in my opinion) the mental model of a TileId better.
I'm also fine with implementing it myself and saw the insert function, but I'm unsure whether that's the correct place, so would like some small pointers for it.
Thanks!
The text was updated successfully, but these errors were encountered:
When inserting a new
Pane
intoTiles
, it returns a newTileId
. The behavior I'd expect is for thisTileId
to consistently refer to the samePane
throughout the lifetime of theTree
.However, this seems this is not the case; when a e.g.
Tabs
container with twoPane
s is changed into aHorizontal
Container
, my firstPane
'sTileId
refers to theHoritonzal
Container
in which thePane
'sTileId
is stored.Would it be possible to keep current
TileId
s always refer to the sameTile
? Not only would this remove the need to manually keep track of whichCustomId
belongs to whichPane
, it would also fit (atleast in my opinion) the mental model of aTileId
better.I'm also fine with implementing it myself and saw the
insert
function, but I'm unsure whether that's the correct place, so would like some small pointers for it.Thanks!
The text was updated successfully, but these errors were encountered: