2012-03-16, 00:34
(2012-03-16, 00:25)Sentir101 Wrote:Sorry I was unclear I guess:(2012-03-15, 22:08)devkid Wrote: Also, is it needed to try both case versions here? It probably does not matter on Windows and on Linux the case of the input 'path' parameter should be the correct one anyway:I think when the wrong case is requested the JSON-RPC request will fail on the XBMC side with an argument error, don't know for sure right now though and don't have the time to test it.
-I think on Windows it wont matter anyway when searching for the actual files.
-But on Linux I think it is not possible to add a source to XBMC that is using the wrong case in the first place. So I guess that on Linux all source strings in XBMC will have the correct case anyway. So you will never get wrong-case'd source strings in the python script. So nothing to worry about here.
-That would mean that the only place where you had to worry about cases would be on Windows in the function that finds the sources using 'startswidth'. When that 'startswidth' is case-insensitive, all should be fine. Thats at least my thinking currently...
(2012-03-16, 00:25)Sentir101 Wrote: EDIT: One more thing, did you try this with a TV source or a movie source, because I just saw I forgot to add the code to get_tv_sourcesI did try with a movie source. I think its quite logical that it does not work because that strings wont match even if you correct the hostname:
smb://opteron185/films/
vs
smb://OPTERON185/Films/
Films <-> films