ScriptsDebugInfo

[byron]

error on line 90: "ERROR: Window Translator: Can't find window scriptsdebuginfo"


Here's the debug log: http://pastebin.ca/2293238


Anyone know what is causing this? I don't understand where it's coming from, and I can't seem to find any reason why it's showing up. I have Dialog.ScriptInfo in my skin, but I don't know if this is what's causing the issue (maybe need to change something there?) I looked at all of the windows/built in controls and xbmc doesn't support a window "ScriptsDebugInfo" so I am somewhat confused.

[Dan Dar3]

I think it's coming from Q:\system\keymap.xml

maybe check yours against the standard one:
https://svn.exotica.org.uk:8443/xbmc4xb ... Keymap.xml

or maybe there's something wrong with your English language?
https://svn.exotica.org.uk:8443/xbmc4xb ... e/English/

[*]Update:

Actually, no, wait, I think it's been lost along the way from this:
http://redmine.exotica.org.uk/projects/ ... v_to=31589

I've got an older source (r31547) of the ButtonTranslator.cpp doing this:

Code: Select all

else if (strWindow.Equals("scriptsdebuginfo")) windowID = WINDOW_SCRIPTS_INFO;

Might need an addition to ActionMapping actions[] to do something like (if WINDOW_SCRIPTS_INFO is still valid)

Code: Select all

{ "scriptsdebuginfo" , WINDOW_SCRIPTS_INFO }

Look for or raise a ticket in the Development tab at the top.

[byron]

Hey friend, thanks for the reply. I'm not gonna lie...what you are describing is a bit over my head. You lost me here:

Might need an addition to ActionMapping actions[] to do something like (if WINDOW_SCRIPTS_INFO is still valid)

From what I can tell, you're telling me that it has mysteriously vanished I guess what I'm concerned about most importantly...is this absence detrimental to the "proper" operation of a skin?

Originally I thought that I had changed something to create this error, but I tested it on PMIII HD and got the same result. I honestly don't even know how to "raise a ticket," so maybe this would be a good time to learn (as any error causes loss of RAM). One question for sure though, would it be better to leave Dialog.ScriptInfo in the skin, or better to remove it?

[BuZz]

use textviewer

xbmc mainline renamed it so I followed suite. I guess I could have left backward compatibility but I didn't think we needed it. if you are running nightly stuff you must be aware that a lot of skin stuff is changing etc.

[byron]

Hey BuZz,

That's what I was thinking it had changed to, thanks. I understand that windows/names/functions are changing, is there a definite source to actually see and compare the changes (current widows vs. depreciated/obsolete or what they have changed to)? I couldn't seem to find anything on the xbmc wiki, it would be nice to be able to make all things current without having a surprise pop up in a debug log at this point I've pretty much just been looking at other skins to see which windows I have compared to those I don't

[BuZz]

well some xbmc wiki stuff is valid some isnt. our wiki is somewhat out of date, but the dev/nightly release isnt out yet, so.

And we don't have enough devs, so feel free to update the wiki as you see fit, although its working noting stuff that is part of 3.2 stable and stuff which is upcoming.