+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Request for debug change (/showthread.php?tid=364584)
Request for debug change - Barry D. - 2021-09-22
I would like to see some manner of starting a debug at a specific point rather than having to wade through reams of debug that usually isn't relevant.
For example: I want to see what KODI is doing when I do a refresh on a movie title, as the scraper doesn't always get the right movie. It's relatively quick on the server and slower than cold snot on a remote. I want to see what's going on and what is taking the extra time but don't want to see everything prior.
RE: Request for debug change - Hitcher - 2021-09-22
Turn on debugging, refresh movie, turn off debugging is the best you're going to get because we need to see all that 'prior stuff' to help understand what system people are using, etc.
RE: Request for debug change - DarrenHill - 2021-09-22
You could even use a keymap (wiki) with the
ToggleDebug application built-in action to temporarily assign the switching on/off to a suitable key on your remote to simplify it even more. Install the keymap, do your tests and then remove the map again to restore the remote key back to its original usage.
RE: Request for debug change - Barry D. - 2021-09-22
(2021-09-22, 09:48)DarrenHill Wrote: You could even use a keymap (wiki) with theToggleDebugapplication built-in action to temporarily assign the switching on/off to a suitable key on your remote to simplify it even more.
Install the keymap, do your tests and then remove the map again to restore the remote key back to its original usage.
I was thinking along those lines with either a magic key combination (for keyboarded systems) and I don't know what for mobile devices (phones/tablets) that don't have an actual keyboard.
In your scenario: I am assuming the keymap function you mention could do a 'click' to set the debug on but how would I access the debug function without getting back to MAIN/SETTINGS/SYSTEM?
Thanks for your help.
RE: Request for debug change - jjd-uk - 2021-09-22
As the name say it's a toggle command so for example
<F9>ToggleDebug()</F9>
Pressing F9 on keyboard will turn debbuging on, pressing F9 again turns it off. Then you can use the Kodi File Manager to find log in special://xbmc then use context menu to select View as text to read the log.
RE: Request for debug change - Barry D. - 2021-09-23
(2021-09-22, 20:01)jjd-uk Wrote: As the name say it's a toggle command so for example
<F9>ToggleDebug()</F9>
Pressing F9 on keyboard will turn debbuging on, pressing F9 again turns it off. Then you can use the Kodi File Manager to find log in special://xbmc then use context menu to select View as text to read the log.
I see what you are saying now, thanks. I'll give it a try.
RE: Request for debug change - Karellen - 2021-09-23
Debug mode can be enabled from a keyboard using ctrl-shft-d.
It is a default mapping.
I am not sure if other systems use f9, but on my windows installs, that is volume down.
RE: Request for debug change - Barry D. - 2021-09-23
(2021-09-23, 03:52)Karellen Wrote: Debug mode can be enabled from a keyboard using ctrl-shft-d.
It is a default mapping.
I am not sure if other systems use f9, but on my windows installs, that is volume down.
Thanks. That works a treat. I checked if F9 was free and it did pop up a volume symbol so I was considering other options when I saw your post.
RE: Request for debug change - DarrenHill - 2021-09-23
Keyboard controls (wiki) gives a full list, for reference.
As standard Kodi uses
+ (and also =) for volume up and - for volume down. F9 doesn't seem to be mapped to anything, but of course there maybe Windows or keyboard driver settings/hardware adding that.Given the ability to remap and Kodi's general flexibility, there are many ways to crack this nut...
