Posts: 244
Joined: Jun 2007
Reputation:
0
The first one!! Nice work.
I suppose that the movieinformation is only visible when selecting one of the movies?
Posts: 1,136
Joined: Jul 2011
Reputation:
18
Balinus
Skilled Skinner
Posts: 1,136
Thanks!
Yes indeed, the movie info appears when you go on a movie with a fading effect. Otherwise, there's no movie info, just the posters for featured and recently added.
Posts: 244
Joined: Jun 2007
Reputation:
0
Is it possible that the new version is not completely uploaded in repository? It's trying to install and then i'm getting into a black screen, after a while it's coming back. When checking the version it's still on 2.5.0. I had to rollback to 2.4.4, to properly use it. 2.5.1 is now marked as 'blacklisted'.
Mac Mini 2,3 | Openelec | Marantz SR-5006 | 2x Monitor Audio Radius 90 | REL T5 Subwoofer | Synology DS213 |
Zotac Zbox ID41 | Openelec | Marantz SR-5003 | 2x Mordaunt Short Genie
Posts: 1,136
Joined: Jul 2011
Reputation:
18
Balinus
Skilled Skinner
Posts: 1,136
2012-04-22, 00:52
(This post was last modified: 2012-04-22, 01:55 by Balinus.)
Yes I have wronfully marked version 2.5.0 in addon.xml. Now 2.5.0 is deprecated and 2.5.1 should be OK now.
If it's not the case, please report back!
edit - The problem appear if you have installed 2.5.0 before I deleted it (it was online for about 12 hours before I saw the bug). The "dirty" way to resolve the problem if it doesn't resolve by itself would be to change the version label in addon.xml from 2.5.0 to 2.5.1 (in Windows, it's located under Users/AppData/Roaming/XBMC/addons/skin.shade.eden.svn). The thing is that 2.5.1 and 2.5.0 are the same version, minus a bogus file that accidently made it's way to the repo. When I uploaded the corrected version (2.5.1), I forgot to change the label top 2.5.1. So XBMC thinks there's always a new version on the repo but the label never changes to 2.5.1.
Again, this problem only appears for people that updated to 2.5.0, during the 12 hours that it was online.
So, if anyone has the problems, please report back. Maybe the quickest way to resolve it would be to upload a "new" 2.5.2 version so that XBMC doesn't go back and forth between 2.5.0 and 2.5.1.