It's really a shame this is happening. I remember reading the change in XBMC where it said something about a change that xbmc would unload skin from memory before applying the new svn skin changes to the directory to help avoid problems being caused with a skin update, but that doesn't look like it's still fixed the issues. Course, depending on user's that might not be using the newest and latest could be what's causing it too if they are using a version with that not in it.
I always recommend to just grab a daily from GIT. I HATED GIT myself, but honestly after setting it up, it's not bad and you get used to things like not being able to look at an svn log using the older svn log maker method, you just use the tortoiseGIT function which works good enough. Almost just as easy to use as SVN thanks to TortoiseGIT.
I also build new skin versions from our svn directly since sometime's i need to see graphic's changes frequently when making them, so this is good to know when our users are having issues with XBMC svn of our skin. I'm glad you make downloadable versions for the users Sharpe, this helps out until they get the little kinks out of the system they are obviously having. Thanks!!
Joined: Dec 2005
2011-02-12 18:46 Post: #11