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
Adding it would just be adding an '|| view == tileExplorer' here, but it would have been intentionally not included because it would break the tilemaps that reference those tiles -- I don't think we do any modification of the .data of assets at all outside the iframe currently and doing so properly would probably be a decent chunk of work (Richard Knoll (@riknoll) to double check?)
I guess another workaround would be to still handle it all in asset frame, and make it so you could set an entry in TileMap.tileset to null and it'd get replaced with transparency next load / on compile or something... but that'd feel real bad to me and feels like something that could result in subtle data loss eventually
Activity
jwunderl commentedon Mar 3, 2023
Adding it would just be adding an '|| view == tileExplorer' here, but it would have been intentionally not included because it would break the tilemaps that reference those tiles -- I don't think we do any modification of the .data of assets at all outside the iframe currently and doing so properly would probably be a decent chunk of work (Richard Knoll (@riknoll) to double check?)
I guess another workaround would be to still handle it all in asset frame, and make it so you could set an entry in TileMap.tileset to null and it'd get replaced with transparency next load / on compile or something... but that'd feel real bad to me and feels like something that could result in subtle data loss eventually
riknoll commentedon Mar 9, 2023
yes, i intentionally didn't include it because tiles are annoying to delete.