Closed aHooder closed 2 years ago
Love u
This should be good to go now :+1:
Could we break the key listener bits out into its own class?
That'd be fine with me. Do you have anything in particular in mind? Maybe a devtools class?
No idea in particular. I'd just like to keep trying to slim down what functionality we put into the main HD plugin class.
Sounds good. I suppose in the future we'll inevitably add more dev tools, so it might be good to move logic for managing that to a separate class.
Sounds good. I suppose in the future we'll inevitably add more dev tools, so it might be good to move logic for managing that to a separate class.
I do have a hotkey class in my dev panel thing maybe can just go into that one it's in
I've moved both shader hotswapping and tile info into a separate class for managing devtools. On second thought though, should we perhaps keep shader hotswapping for non-developers in case we want to try fixing shader bugs through the support channel?
I've moved both shader hotswapping and tile info into a separate class for managing devtools. On second thought though, should we perhaps keep shader hotswapping for non-developers in case we want to try fixing shader bugs through the support channel?
Not sure how I feel about that what if we add a enable debug in config Panel off by default ?
Adds the following overlay to help with modifying tile overlays, underlays and materials. Currently it's toggled by the hard-coded keybind Ctrl F3, and it only works while in developer mode.
This also restricts shader hot-swapping to developer mode.