(2014-05-02, 09:57)Martijn Wrote: (2014-04-30, 23:29)Jeroen Wrote: (2014-04-28, 01:28)mortstar Wrote: Something I've noticed with 'recommended episodes' is that it always defaults to list view. After every update to the data or after a reboot, I have to reset the view to slide. This doesn't happen in 'new episodes' which keeps its view setting. I wasn't sure if this is a skin or system issue.
(2014-04-29, 12:30)Jeroen Wrote: Update after talking to Unfledged about this. The reload property in the onclick action of the home menu button is the cause of this. Basically every time the reload takes place, the URL changes so XBMC treats it like a new folder, thus applying the default viewtype as a result.
Unfortunately removing the reload property from the link also means the container will not get reloaded automatically, obviously. You will need to exit and re-enter the window to get a refreshed list. Especially when watching episodes, to me that is a big negative.
So, a new update on this. I got a nice surprise from Unfledged, a shiny new script specifically made for this purpose
The Library Data Provider add-on was never really intended to be used in the library, but for Gotham's new list filling feature (that's how it is used in the homescreen shelf widgets). It works in the library, but as is clear with some drawbacks.
This new script will remember the view settings and the content will automatically be updated (at the cost of a small performance hit compared to the Library Data Provider script)
So, I replaced the script used in the library, and reinstated the "Watchlist" name in the home menu.
This means that as of now there is a new required add-on.
The script isn't available on the XBMC repo, so you will need to install it manually. Hopefully it will be made available there, so it can be automatically installed. For now, you can download the add-on here:
script.watchlist
If you do not install this add-on you will get a "dependencies not met" error when installing or updating reFocus.
Note that the Library Data Provider is still needed by the skin.
I hate the fact we will end up 10 more scripts just because instead of fixing one service/script that provide most/everything.
why another script instead of fixing current Library Data Provider script so it doesn't show this issue.
i have nearly adapted skin widgets script to combine all of this.
so from my pov all those extra script are just repo pollution and doesn't make maintaining it any easier.
all this keeps running in the background when not being used any more. also this will show up in the repo list and people just wouldn't know any more what they want/need or should install.
i will discuss this internally what we will do about this as things should be made user friendly and not creating confusion for users that they again need to configure another script and that the old skin widgets isn't used any more but will still be running in the background.
of course if there's no other way it won't be an issue.
Why another script? 3 reasons
First, I disagree that having one script to do everything is always the best way. This fix can be done in Library Data Provider - it just needs a way to return results from the plugin element without relying on the cache - but that adds extra complication to the script for the sake of a single skin. Not to mention this would require a fair bit of refactoring of that script, compared to writing a very very simple script to do it.
Second, your version of skin widgets is coming. I could add this to Library Data Provider, but that could instantly be obsolete and this same problem could need fixing again. A separate script means if your version doesn't include this fix, it doesn't need fixing in the future.
Thirdly, most of what else the Library Data Provider does can be done with playlists/library links, so its technically possible with this script to actually not need Library Data Provider (whether thats wise is a different discussion!), so actually reducing the number of background services by one.
I'm quite happy, though, to make a pull request to the Library Data Provider script. I'm equally happy to wait for your Skin Widgets which, now you know of this problem, I presume will already have the solution within, so making the watch list provider obsolete
Up to you.