Kodi Community Forum

Full Version: [REQUEST] Debug type screen like Alaska
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Pages: 1 2
One of the most helpful things I ever found was the debug mode for Alaska. That lets you know .xml you are in. I really think Confluence should have it since it's the default skin, the skin that everyone has, and the skin that has every XBMC feature (addons, PVR, etc) built in.

Image
Image

All it is is a setting to check, an include:
Quote:<include name="Debug">
<control type="image">
<posx>0</posx>
<posy>0</posy>
<width>1280</width>
<height>20</height>
<texture>common/black.png</texture>
</control>
<control type="label">
<posx>4</posx>
<posy>0</posy>
<width>1280</width>
<height>18</height>
<aligny>center</aligny>
<font>Medium</font>
<textcolor>white</textcolor>
<label>$INFO[Window.Property(xmlfile)] / $INFO[System.Screenresolution] / $LOCALIZE[158] - $INFO[System.FreeMemory]$INFO[System.CurrentWindow / ]$INFO[System.CurrentControl, / ]</label>
</control>
</include>

And a simple include at the bottom every .xml:
Quote:<control type="group">
<include>Debug</include>
<visible>Skin.HasSetting(debugmode)</visible>
</control>
What would be even better is to have all this info in the actual built-in debug mode.
I gotta admit it's probably one of my favorite features...It definitely helped me learn skinning. I took a peek at a new build today to see what I have to do for addons, and copied the Alaska debug code to know where I was. Luckly, for me atleast, it shouldn't be too much work.
+1
great idea
One question for to be sure, Is "$INFO[Window.Property(xmlfile)]" working just on latest SVN? I try with stable build and it's not working.
Looks like that property was added 1/18/10
Which of these things do you actually need?
Hitcher's suggestion to add $INFO[Window.Property(xmlfile)] to the actual built-in debug mode would be best. That would help many aspiring skinners and modders know what .xml they are in. And then it wouldn't be skin dependent.

Case point:
I tried a new build(29005) to see what I have to do skinningwise for add-ons. So I copied Alaska's debug code to Confluence so I new for sure what .xml addons was in.

Or somebody wanted to change the look of Rapier's pausebar all he'd have to do is hit dubeg mode then pause a movie and he'd know to edit dialogseekbar.xml
What about window name?
The .xml name is probably the most helpful, window name is good too.
I reckon a advanced setting for skin debug that shows on the right hand side (so its not over the other debug)

xml filename
window title
mouse x/y
current focused control ID and type
r29100 should do the trick. Enabled via <debugging>true</debugging> in skin.xml.

It renders underneath the debug info. Not sure whether it should render all the time or only when XBMC debugging is enabled. Thoughts?

Cheers,
Jonathan
I know I always run debug when I'm skinning to watch fps and stuff but I'm not sure that's common practice.
Last nightly I tried too much was broken(28991)...I'll give it a week or so before I try this out, thx for the change though...
Pages: 1 2