Thanks for responding, Nick! Just a few quick follow up comments:
-
Describing focus could be more complicated than a brush swap, but I would then propose that describing hover could be more complicated than a brush swap, as well. As long as we have a simple option for describing it (brush swap) and events for doing more (see point 2), then I think we’re set! For sound, I would propose a sound triggered upon focus, just like sound on a hover, is most important. Having an option to signal a failed focus might be nice, too, but less important, IMHO.
-
Sweet!
-
I agree you wouldn’t want to lose any of the current functionality that allows switching between UI and viewport. However, I would definitely propose that we need a simple, clean solution for preventing it when we know we’re in a state where it should never happen (e.g. typical pause menu in most games).
-
Gotcha. I didn’t realize it’s not intended for use outside development, but that totally makes sense. If it’s a debug tool, maybe have it off by default? It took me forever to find out how to turn it off cause I didn’t even know what to call it when searching in the editor or on the internet
