• 11 Posts
  • 13 Comments
Joined 1 year ago
cake
Cake day: June 30th, 2025

help-circle










  • My issue with this illustration vs “the dress” is that in the dress, the background is bright, not a darker blue.

    In theory, this illustration just serves to show that nobody should be seeing “the dress” as white and gold. Thy do, and that breaks my brain, but I still feel that there is no logical way for that to be justified (and yes, I read all the research).





  • I went with a stack pattern and priorities.

    Within a priority the last “layer” to activate is the only one to receive inputs. The priority system just means that if a layer from a lower priority gets activated, it doesn’t take over until the upper layer is empty.

    It’s a bit stricter (only one layer active at all times), but you can always subscribe to inputs from multiple layers to achieve what you were describing.

    The main advantage here was that you can safely rely on enabling/disabling layers without ever getting a conflict… If some popup comes in over your menu, the popup is in charge until it’s closed. No need for them to communicate, and you reliably know that inputs will eventually return to the menu properly, even if something else gets interposed.

    And since it’s tacked onto the existing system, you can always have parts of the code that ignore the layer system entirely if necessary (like a mute button that has to work across all systems/menus for example).