The goal was:
Get the Switch Tile Client Creator working with the Switch Tile Client Editor
Result is success. There were a few bugs along the way. Most being mismanagement of what got added and removed at various points and what should belong with what.
That add/remove mismanagement got me thinking more about code organization. I had built add and removal automation but still get confused in certain situations. This one being what I would call a multi-level GUI.
I'm trying to better understand this multi-level GUI by visualizing a grid of tiles with various different blocks placed on some of the tiles. I highlight only the ones that belong to a group. With those blocks in front of me, I am looking at an editing hub that gives two choices; add more blocks to the group or change the properties of any number of the blocks I picked out. Selecting either of these choices and making changes will need to be translated back to the hub. So, do I leave the hub open and halt any actions in it while editing or do I just consider the hub a third separate system that gets removed while editing?
No comments:
Post a Comment