@pro-forma-nails True, I don't tend to use cyclical references; in that case, instead of rejecting duplicate entries, you could set them to the top like this:
but if you find yourself in such a twist, I'd switch to using a Stack; the above would pretty much simulate a Stack with our List by manually managing its order, but we can eliminate such need and potential for error by using a Stack. Stack has some nifty functions such as Pop and Push that make it ideal for order-concerned usage: Pop removes and returns the top item, Push adds an item to the top of the stack. Here's what it could look like:
(I added some safety checks for the while loops, they ideally shouldn't be needed but of course the road to hell is paved with "that shouldn't happen"s 😅)
In the simple approach I use List for its easy Remove functionality, which Stack does not have; you can only Pop or Peek at the top most item (Peek retrieves the top item without removing it). But by creating a tempStack to rebuild from we can mimic List.Remove behaviour for closing out a selected menu. Then Escape usage looks like this:
This 'snippet' got a little verbose so if you'd like you can take a gander at it on github~ in that version I've turned the loops into a shared RemoveFromStack function so we don't have to write the loop logic twice, and added a ToggleMenu function.
IF you wanted even finer control, say, being able to close groups of menus together (maybe you have a PlayerUI that opens new windows for StatsUI, TalentsUI, whatever) you could add a new MonoBehaviour to menus like MenuGroupTag with variables like bool isGroupLeader and string groupID, then when you close a menu you can look for the MenuGroupTag and check if isGroupLeader, if so, close all that match its groupID. If anyone would like to see an example of that just send a request to your friendly neighborhood battlecat (=ↀωↀ=)~
stormborns
ellievsbear
areudirty
janainaart
pixelskylines
discoholicmusic
origamiaround
snowghoul
2087
