Environment qL asset importing doesn't work properly

[gadfly16]

First of all, the importing is unnaturally slow.

Second, full path of the imported assets has both slashes and backslashes which prevents to save the asset after modification.

Note: something must went wrong during refactoring. The version in the master branch works properly for both windows and linux.

[johnnyquest]

There wasn't any serious refactoring, mostly the changes were about the node to be more verbose (to allow for easier debugging in batch/renderfarm mode).

[johnnyquest]

Btw, there are several examples for this node is the examples/workflow folder (illustrating various project set-ups). One of them could be extended to include asset loading via Env qL.

[johnnyquest]

also see #224 for planned RFEs.

[johnnyquest]

From Dragos Stefan:

We're using Env qL quite succesfully but we don't seem to be able to load otls from paths we specify in the .py file.
The OTL_PATTERN variable is written correctly, but libraries don't load, even after doing a refresh assets.

Is this a windows-only bug? (Gergo also had problems like this on his windows machine, but he said it worked okay on linux)

[johnnyquest]

Ok, so the problem seems to be the asset using the colon (":") as path separator, even on windows (which is obviously a broken behavior to begin with.)

[johnnyquest]

Dragos says this fixed the issue for him. We should get some more feedback from Gergo/Mate before closing this issue?

[johnnyquest]

@gadfly16 i wonder if this thing got fixed. did i fix it with that commit above? :DDD

[gadfly16]

The asset is apparently broken. I need to fix it ASAP. The only problem is testing, since it needs to work on all OSs. I will look into this, when I can spend some time next to a Win machine.