[Rich.T.]

Rich, this was how the original add-on did it - so I'm surprise you are having a problem with it. And as it happens I am testing and running on Windows.

You know; it beats the hell out of me.
The original version worked fine (in it's way) and this behaviour only started to manifest recently, I believe. I think that the logs speak for themselves, though. It just seems bizarre to me.

As it happens the correct way of doing this I believe is to use "os.sep"

Rob

Thanks so much for that, Rob! I was trying to find such a function earlier (probably after you had made the above post, too), but gave up after a little while.

I changed the lines to:

Code:

extrasDir = basepath + os.sep + xbmcaddon.Addon().getSetting( "extrasDirName" ) + os.sep

and

Code:

dirpath = basepath + os.sep + dirname + os.sep

so it now seems to work fine in both Linux and Windows.

I know that no one else has had the same problem, but it might be worth committing as a change because it can't hurt really, can it?

It's worth thinking about, anyway.

Rich.