trailing slashes in a workdir path

[remyla]

users could configure a work dir path like /home/user/work/ (with trailing slash)
if the assets we want to track have an absolute path like /home/user/work/production/chars/rabbit.blend, the system is now proposing to the user to track the file using the path production/chars/rabbit.blend but we would like this path to remain as /production/chars/rabbit.blend

we would like a system to work even if the user wants / as a local work dir

[Baenshee]

Wouldn't the use of / as a local workdir be like not using a workdir and prevent the simplified creation of workdirs ?

[remyla]

maybe we could have a switch, not to take a '/' workdir into account if we
still want the UI to ask the user if he wants to declare a new workdir?
leave the '/' for the moment if it is asking a lot of modifications. the
trailing slash support is the most important

Rémy

On Thu, Jun 11, 2015 at 12:21 PM, Mathieu [email protected] wrote:

Wouldn't the use of / as a local workdir be like not using a workdir and
prevent the simplified creation of workdirs ?

—
Reply to this email directly or view it on GitHub
#29 (comment).

[Baenshee]

Or have a toggle to enable/disable the use of workdirs ?

[remyla]

well, the switch I spoke about was about adding a condition in the program,
not a switch visible from the UI, if this is what you meant. As I said,
having the same behavior as it is now, but with support for trailing
slashes when they occur, would be the priority. If you think of an
enhancement, please elaborate, I will be happy to hear the idea

On Thu, Jun 11, 2015 at 2:37 PM, Mathieu [email protected] wrote:

Or have a toggle to enable/disable the use of workdirs ?

—
Reply to this email directly or view it on GitHub
#29 (comment).

[Baenshee]

The support for trailing slashes has been added in my last pull request. I'm still looking for a way to manage the / workdir