(2017-02-13, 21:23)Alanon Wrote: Well, instead of going backwards, let's try to go forward. I've had a thought and made some workarounds, let's see if it's good enough.

DOWNLOAD 2.0.9

I'm beginning to realise that perhaps it would be good if I got control of the first post, the various versions and changes are starting to confuse even me...

(2017-02-13, 21:36)jdig4240 Wrote: Guess what, THAT FIXED IT! Thank-you. So, what was it?

(2017-02-13, 21:59)Alanon Wrote:

(2017-02-13, 21:36)jdig4240 Wrote: Guess what, THAT FIXED IT! Thank-you. So, what was it?

Well, best I can figure, at some point, something changed in either skinshortcuts or skin helper widgets, or both, that also changed the referencing to content type which controlled the result of an item being clicked on. I never actually touched the particular piece of code that messed with widgets, which could perhaps mean that the code was dependent on some other element that I have changed, though I'm unclear as to what or why. That's why it took me so long to figure it out. I can't even guess as to what made the older versions work out of the box, and probably never will.

Anyways, looking at your logs again and finding those video content errors steered me in the right direction. The persistent widgets use a widgetTarget property in addition to the content categorisation, which is why they worked in the first place. The reloading variants used only videos as a category, which means that anything besides that would fail/not register. After confirming that, it was just a matter of migrating the property check to apply to the non-persistent widgets.

It'd be interesting to know if this fixes everything, even stuff like add-ons widgets, or music/genre widgets, etc. Things that were never in the videos category presumably never worked properly, but I've actually never used them and it hadn't even occurred to me until after I've finally fixed the damn things.

(2017-02-13, 22:02)eurogroovem5 Wrote: @Alanon

Is there an easy way to edit the transparency of the hub menus?

(2017-02-13, 22:10)jdig4240 Wrote: Nice work, I appreciate you taking the time to figure this out. Thats beyond my skill level, but im slowly starting to learn skinning basics. Thanks again Alanon.

(2017-02-10, 22:46)Alanon Wrote:

(2017-02-10, 22:26)PantsOnFire Wrote: Thanks for the reply. Saw ur post this morning but just tending to it this evening.
I should say... My version is actually OSMC, I don't know if that would make a difference...

From system info screen...
* OSMC running kodi 17.1-RC1
* OS: 2017.02-2 (kernel : Linux 4.4.27-7-OSMC)

I should be fine right? How can I tell which GUI version is running in this build? Or is it implicit in the overall kodi revision number? (17.1-RC1)

You're on the right track, the gui gets a version bump on every new version of Kodi, so you're covered. By definition, that can't be the problem. I've never used Kodi on a distro before, but from what I've read, folks have had these sorts of problems with gui errors before, just not with an easy solution. The issue for them had been something with updating the dependency repos, which I'm pretty sure doesn't apply here. Off the top of my head, what you can do is double-check that the dependencies are indeed getting installed properly, and in their proper versions (maybe try to pull them manually from the repo?). The second thing to try to do is to unzip the skin itself into Kodi, restart, and then enable it from the addon browser, and see if it will go.

Oh, and this might be a silly thing, but I've only just noticed that in your previous post you said you downloaded the skin from the OP. If by that you mean the first post in the thread, then that might be the whole issue right there. I myself don't have any control over the thread, I just wanted to mod the skin for my use, and things sort of took off. The first post is pretty much totally outdated. It contains only the mods done by Guilouz, which are discontinued, as the thread title states. It's a very rough version for Krypton, with a lot of problems. My versions are strewn across the thread over the last couple of pages (the most recent one is just above your post). As I said, this might be a superfluous comment, but it's worth mentioning, since it usually the little things that get you.

(2017-02-10, 22:46)Alanon Wrote:

(2017-02-10, 22:26)PantsOnFire Wrote: Thanks for the reply. Saw ur post this morning but just tending to it this evening.
I should say... My version is actually OSMC, I don't know if that would make a difference...

From system info screen...
* OSMC running kodi 17.1-RC1
* OS: 2017.02-2 (kernel : Linux 4.4.27-7-OSMC)

I should be fine right? How can I tell which GUI version is running in this build? Or is it implicit in the overall kodi revision number? (17.1-RC1)

You're on the right track, the gui gets a version bump on every new version of Kodi, so you're covered. By definition, that can't be the problem. I've never used Kodi on a distro before, but from what I've read, folks have had these sorts of problems with gui errors before, just not with an easy solution. The issue for them had been something with updating the dependency repos, which I'm pretty sure doesn't apply here. Off the top of my head, what you can do is double-check that the dependencies are indeed getting installed properly, and in their proper versions (maybe try to pull them manually from the repo?). The second thing to try to do is to unzip the skin itself into Kodi, restart, and then enable it from the addon browser, and see if it will go.

Oh, and this might be a silly thing, but I've only just noticed that in your previous post you said you downloaded the skin from the OP. If by that you mean the first post in the thread, then that might be the whole issue right there. I myself don't have any control over the thread, I just wanted to mod the skin for my use, and things sort of took off. The first post is pretty much totally outdated. It contains only the mods done by Guilouz, which are discontinued, as the thread title states. It's a very rough version for Krypton, with a lot of problems. My versions are strewn across the thread over the last couple of pages (the most recent one is just above your post). As I said, this might be a superfluous comment, but it's worth mentioning, since it usually the little things that get you.

(2017-02-13, 22:39)eurogroovem5 Wrote: @Alanon

Argh. Im trying to get this effect.

http://imgur.com/a/KMjOv#2Yzub6N

Its from another thread here. The only lead that I got was to get Kodi Texture Tool and edit the xbt. Can't find the xbt, but I do see what I believe to be the contents of the xbt in the same folder. I test it out. I found the cursor.png, inverted the colors, reloaded Kodi and found that it worked. Am I in the right direction? Is the file that I need to edit here?

(2017-02-13, 22:39)eurogroovem5 Wrote: @Alanon

Argh. Im trying to get this effect.

http://imgur.com/a/KMjOv#2Yzub6N

Its from another thread here. The only lead that I got was to get Kodi Texture Tool and edit the xbt. Can't find the xbt, but I do see what I believe to be the contents of the xbt in the same folder. I test it out. I found the cursor.png, inverted the colors, reloaded Kodi and found that it worked. Am I in the right direction? Is the file that I need to edit here?