2019-07-21, 00:07
Been diving into doing some heavy customization without the the use of modules (like pyxbmct, etc) but hit a few roadblocks so wanted to check on a few things.
What doesn't work in scripts/addons when it comes to XMLs, that does in Skins? Examples below specifically that I am looking at:
1. Variables and Constants? If so, am I overlooking an obvious difference?
2. Includes (file and name)? If so, am I overlooking an obvious difference?
3. RunScript()? (Haven't tried just yet)
4. Params
Also, is there a way to pull the image used in an image control from the script invoking the XML directly using XBMC functions, members, or attributes?
Here is why I am asking the probably already beat to death questions I couldn't find an answer to.... Working on generating the custom windows for the script, but want to allow the use of 3rd party artwork modules to pull the artwork/skins information from dynamically. The code part I have already achieved more or less, aside from the fact if a fork is done then all artwork has to be under the same folder names and can have only one set per fork. I suppose that will work, but wanted to allow multiple artwork themes per fork of the artwork module.
I suppose ultimately I could limit it to single set of images, and work with color theming instead but then I still fall into the issues where variables and constants seem to not work in the script.
Any feedback would be greatly appreciated on this area of work since it is new to me.
What doesn't work in scripts/addons when it comes to XMLs, that does in Skins? Examples below specifically that I am looking at:
1. Variables and Constants? If so, am I overlooking an obvious difference?
2. Includes (file and name)? If so, am I overlooking an obvious difference?
3. RunScript()? (Haven't tried just yet)
4. Params
Also, is there a way to pull the image used in an image control from the script invoking the XML directly using XBMC functions, members, or attributes?
Here is why I am asking the probably already beat to death questions I couldn't find an answer to.... Working on generating the custom windows for the script, but want to allow the use of 3rd party artwork modules to pull the artwork/skins information from dynamically. The code part I have already achieved more or less, aside from the fact if a fork is done then all artwork has to be under the same folder names and can have only one set per fork. I suppose that will work, but wanted to allow multiple artwork themes per fork of the artwork module.
I suppose ultimately I could limit it to single set of images, and work with color theming instead but then I still fall into the issues where variables and constants seem to not work in the script.
Any feedback would be greatly appreciated on this area of work since it is new to me.