Fix exporter on non-windows operating systems

[drewcassidy]

The root directory path is hardcoded to a backslash currently, which breaks support on non-windows operating systems. This replaces that with a forward slash, which should work on all operating systems. see #4.

[drewcassidy]

I'm honestly not sure why this failed in the linter since the only line I changed didnt create a warning in the output log

[moppius]

I'm honestly not sure why this failed in the linter since the only line I changed didnt create a warning in the output log

Looks like there's a config problem with the linter, sorry about that - I will investigate!

Good catch, and thanks for the PR. We hadn't tested the addon on Linux or MacOS yet, so thanks for taking care of this!

[moppius]

So apparently this is a bug introduced in PyLint 2.5.1...
Also mentioned in a different bug here - looks like they don't properly respect relative imports, and they aiming to fix it for PyLint 2.5.4!

I'll pin PyLint to an older release for now and re-run the checks.

[moppius]

If you merge latest master in to this branch now, linting should pass!

I'm considering maybe removing the RELATIVE_ROOT thing entirely, though, and instead requiring that the user defines a valid path by browsing to it, and we'd disable all UI until they had done that.

Out of interest, when the Project Source Path is set to ./, what would you expect the behaviour to be?

As a studio, we always want the stored paths to be relative to an absolute location that might differ from machine to machine, which is what the Project Source Path represents.

Right now it seems like it can actually output exported collections into the Blender install location when set to ./, which seems like a bug.

[drewcassidy]

if it's set to ./ I'd expect it to place files relative to the filesystem root

[moppius]

Thanks! Let us know if anything else breaks on MacOS, most of us at Embark don't use that as a primary development platform with Blender, so there may be other issues we haven't run into.