[Blurayx]

@jurialmunkey,

I only have one location

when I click settings 


it takes me here, Not directly into the weather settings. is this the normal sequence?


I have the same issue on my Shield TV and iMac

Thanks

[jurialmunkey]

@Blurayx - Yes that is normal. The "sun" icon will directly open the weather settings.

[Blurayx]

@Blurayx - Yes that is normal. The "sun" icon will directly open the weather settings.

Ok, Thanks.

[Blurayx]

@Blurayx - It works fine for me. Do you have multiple weather locations set in your weather addon? By "change location" it means "cycle through the locations you have set", not "set a new location".

Ok, I understand now 

Thanks

[essjaygee]

Firstly jurialmunkey, congratulations and thank you for a great-looking and well-thought-out skin in Horizon.

I have a question about the MusicVisualisation/MusicOSD screen that I hope someone could help me with. Is it possible to prevent the song/artist/etc info (at the bottom of the screen from fading out when the OSD controls (at the top) fade out? I like to keep the song info on the screen all the time. It's the sort of option I'd expect to see in the Skin Settings->Video/Music OSD options, if it exists.

Thanks very much in advance.

[jurialmunkey]

@essjaygee - press info on your remote or i on keyboard will show osd info.

@trantrung - Builds are full of dodgy piracy addons. Do a clean install of just kodi and the skin and see if you still have the crashes. Otherwise I can only assume its one of the dodgy addons the build has installed. I don't get any crashes,so I can't look into it - particularly if you don't give me a debug log.

[Joe23rep]

how old is the build? in other words- which Version off the horizon skin is used in the build?  

cuz when i installed the Version from a few month ago i had the skin crush from time to time on my raspberry pi. 

with later versions i never expierienced any crashes anymore. not on android tv box, tablet or even on small low powered devices like rasperry. 


so either its really a shitty add on which he used in the skin or a really old version of the skin. the Version in the offical repo and probably 10 versions prior worked already fine for me

its easy too see- jurial build in many new settings like icon mode, effect section in settings, ungroup widgets etc.

[trantrung]

@trantrung

You obviously ignored the forum rules when you signed up. Please read them and become familiar with our requirements.

You will need to clean your system of all offending addons to receive support here, or head over to those other download sites for assistance.

Your posts will be removed until a clean debug log is submitted.

Understood. Thanks

[jdig4240]

Man, love this skin, really do. Unfortunately im getting  constant crashes also. Mainly while just scrolling up or down the main tabs. Ill try to get a "Clean" log. Thanks for the skin.

[jurialmunkey]

Man, love this skin, really do. Unfortunately im getting  constant crashes also. Mainly while just scrolling up or down the main tabs. Ill try to get a "Clean" log. Thanks for the skin.

Note that the more widgets you use and the more items they have in them, the heavier the load on the skin. I've found the ungroup widget option creates a much heavier load on my system.

Also, can you try the latest git commit that I've made. I introduced a limit to the number of items in each widget, which should hopefully help with performance -- my guess is that the crashes are happening because you are running out memory (wild stab in the dark, but I have a feeling that might be it if you are using a low powered / low memory device).

The default item limit is now 10 (i.e. each widget will only show 10 items). This can be changed to 25 or 50 in Skin Settings > Home > Widget item limit (its down the bottom).
Try the skin out using only 10 items per widget (default setting on latest github version) and let me know if it makes a difference.

[jdig4240]

Man, love this skin, really do. Unfortunately im getting  constant crashes also. Mainly while just scrolling up or down the main tabs. Ill try to get a "Clean" log. Thanks for the skin.

Note that the more widgets you use and the more items they have in them, the heavier the load on the skin. I've found the ungroup widget option creates a much heavier load on my system.

Also, can you try the latest git commit that I've made. I introduced a limit to the number of items in each widget, which should hopefully help with performance -- my guess is that the crashes are happening because you are running out memory (wild stab in the dark, but I have a feeling that might be it if you are using a low powered / low memory device).

The default item limit is now 10 (i.e. each widget will only show 10 items). This can be changed to 25 or 50 in Skin Settings > Home > Widget item limit (its down the bottom).
Try the skin out using only 10 items per widget (default setting on latest github version) and let me know if it makes a difference.

Ok, definitely will try it.  Thanks

[Sheepish]

2. Nextup in the info dialog doesn't use any plugins. It is just a container that shows all episodes in the library for that particular show dbid. The container is sorted by playcount. Unwatched episodes have a playcount of 0 so they show first (and when there are multiple items, the fallback sort order is by episode number so that earlier episodes show first). Unless there is something wrong with the playcount in your db, it should work.

Ah, I was getting confused with the NextUp service add-on
I checked the playcount in the db files and found my 0's were NULLs but i think this is normal?
I had a poke about in the skin xml and found DialogVideoInfo.xml:154 was

Code:

<content limit="3" sortby="playcount" sortorder="descending">

Wouldn't this mean this feature wouldn't work for anyone if it was prioriting episodes that had been watched, exactly as I was finding? Unless it's something bizarre and improbably like NULLs are "high" for others but low for me? I know some DBMS's can be toggled in this way...

Anyway I changed it to ascending and it's working perfectly, thanks

[jurialmunkey]

@Sheepish - EDIT: Actually you are totally correct. I just figured out what happened -- it was totally a stupid mistake on my end. Originally I had it as "sortdirection=descending" which is incorrect because it should be "sortorder" (not direction) -- So originally sortorder setting wasn't even having any effect because it was the wrong syntax (and it was just defaulting back to sorting ascending). I think when I was getting ready for the repo it showed up as being the incorrect syntax and I changed it to the correct "sortorder=descending" but didn't check that that was the direction needed. Will fix it now! Thanks for your detective work!

[Sheepish]

@Sheepish - EDIT: Actually you are totally correct. I just figured out what happened -- it was totally a stupid mistake on my end. Originally I had it as "sortdirection=descending" which is incorrect because it should be "sortorder" (not direction) -- So originally sortorder setting wasn't even having any effect because it was the wrong syntax (and it was just defaulting back to sorting ascending). I think when I was getting ready for the repo it showed up as being the incorrect syntax and I changed it to the correct "sortorder=descending" but didn't check that that was the direction needed. Will fix it now! Thanks for your detective work!

Hah, it's always something simple.

So now we've solved that one....
Is there anything that can be done about the glitchy jump in certain views. For example, when I enter the list view the first and top item is highlighted, then I activate the scrollbar, move the scroll somewhere, return to the list item, the new item is highlighted, still as the first visible item, but as soon as I move to the prev/next item it centres it. Could it be possible to only centre the cursor if it is already centred? Honestly, sometimes it takes my brain a second or two to focus on where the cursor has moved to because I expect "down" to move to the second visible item, not the 5th etc. I hope that makes sense

/edit - and thanks for the reputation!

[fonzie]

I am having a problem with the colorbox script giving me an error right on bootup. And the outlines don't match the poster. I have it installed on two of my Nvidia Shield TVs and have the same issue. I'm thinking it has to do with conflicting prior versions of colorbox still lingering. I installed version 2.0.5.1 from Marceldvt repo, if I'm not mistaken. I got it running fine on my ubuntu machine so I know it's possible. I just wanted to get a few tips on how to resolve this before I do a clean install of Kodi and have to reinstall all my addons again.

https://pastebin.com/LYAWpgff

**I'm also having issues with the Extended info script. I reproduced this error by opening Kodi, navigating to the first movie in my library, pressing info, and then down on the actor's image:
https://pastebin.com/Ye5Gn6fB