[scott967]

So far 0.1.7 is looking good here.

scott s.
.

[roidy]

v0.1.8-alpha

Add go to definition and peek definition for $VAR and $EXP

[scott967]

Wow that's great.  Now if you could tackle includes ---

scott s.
.

[roidy]

Yep, it's on the list of things to add, let me know if there's anything else that could be useful.

[scott967]

Also would be nice to do the same with $ADDON[addonid number] derived from addonid strings.po.  When doing customized xml for an addon's dialogs it's a pain having to find the addons localized strings (true also for an addon's settings.xml but that isn't much of a skinner's problem).

scott s.
.

[roidy]

When you say do the same thing with $ADDON do you mean decorate the file or peek/go to their definition?

[scott967]

Just the decoration so I understand what a label is supposed to read.

scott s.
.

[kittmaster]

Just found this and installed...what a major help...ty!

[roidy]

Wow that's great.  Now if you could tackle includes ---

scott s.
.

v0.1.9-alpha

Add goto definition and peek definition for includes.

Link in first post.

[kittmaster]

Wow that's great.  Now if you could tackle includes ---

scott s.
.

v0.1.9-alpha

Add goto definition and peek definition for includes.

Link in first post.

OMFG dude: Legend.....

I've been waiting for something like this... Sooooooooooooo much Fuc ******* ing easier to see things without having to use that worthless search and peck feature in VSCODE.

The one question I did have about this tool, If I have strings in my local language files, particularly English, is there a way to make it look there also for strings vs just the Kodi core english files? Or add an option in setting to allow users to have it look in the lang of their choice (not sure if it supports non english or not)?

This has been a great addon, truly. Thanks for it.

[roidy]

Yep, the extension first checks Kodi's built in English language file and then the skins English language file at the following directory, using VSCode's current workspace folder which should be your top level skin folder, ie. skin.madnox, as the root.

skin.madnox/language/resource.language.en_gb/strings.po

You need to open your skin in VSCode using "File->Open Folder" and then selecting your skins top level folder. That way VSCode's workspace folder is correctly set to your skin's root directory.

I've downloaded your Madnox skin from GitHub and everything seems to work fine:-

[kittmaster]

Here is an example:

[kittmaster]

You need to open your skin in VSCode using "File->Open Folder" and then selecting your skins top level folder. That way VSCode's workspace folder is correctly set to your skin's root directory.

I've downloaded your Madnox skin from GitHub and everything seems to work fine:-

That is exactly how I do it.

And for almost for the most part, it does work fine, just a few it doesn't.

[roidy]

Is there anywhere I can download your version of Madnox with the script-tmdbhelper-recommendations.xml file and current strings.po so I can do some testing.

The current decorator functions are really janky and could do with being rewritten.

[roidy]

Forget that, I see the problem.

The extension looks in resource.language.en_gb your skin uses resource.language.en_us.

I'll make some changes to set the default language and put up a new version.