2022-04-19, 14:40
(2022-04-19, 09:30)DiMag Wrote: Skin.ToggleDebug toggles DEBUG on/off, not DEBUG INFO. It sounds weird, but try it yourself and you shall see. (BTW you don't need make a shortcut for Skin.ToggleDebug. It is already built-in as keyboard shortcut CTRL+SHIFT+D.)No, your wrong. (toggledebug), or CTRL+SHIFT+D toggles the debuginfo, and (skin.toggledebug) toggles the skin debug info that exposes the current skin .xmls and buttons, thats what you said you wanted. Did you even try the command, cause it works for me.
In fact it is not so much weird as an omission to state clearly that the debug view we are talking about here ---expose or not expose active windows/lists/buttons--- has nothing to do with taking or not taking system debug logs ---the ones to be posted in order to help troubleshooting. Before posting, I fired up CTRL+SHIFT+D. The screen, already polluted by debug info, got further and even more unbearably polluted by senseless info about amount of memory in use, fps, and what-have-you. Pus the indication where all this gets saved to. So before that no debug log was taken. Debug view isn't debug logging, and my request for a switch to toggle it on/off persists.