Change Details

Asset catalog paths are of the form `A/B/C`. The difference with file paths is: - Asset catalog paths are always absolute, so there is no initial `/` required to distinguish between absolute and relative paths. - Backslashes are not valid as separators. When reading catalog paths (either from a definition file or from the UI when creating/renaming catalogs) they should be normalized. When loading from file, leading and trailing slashes are already stripped. This task is for: - [ ] Replace `\` with `/` to accomodate Windows users. - [ ] Strip leading/trailing slashes when user inputs a path on the UI (i.e. via RNA setter).

Asset catalog paths are of the form `A/B/C`. The difference with file paths is: - Asset catalog paths are always absolute, so there is no initial `/` required to distinguish between absolute and relative paths. - Backslashes are not valid as separators. When reading catalog paths (either from a definition file or from the UI when creating/renaming catalogs) they should be normalized. When loading from file, leading and trailing slashes are already stripped. This task is for: - [x] Replace `\` with `/` to accomodate Windows users. - [x] Strip leading/trailing slashes when user inputs a path on the UI

Asset catalog paths are of the form `A/B/C`. The difference with file paths is: - Asset catalog paths are always absolute, so there is no initial `/` required to distinguish between absolute and relative paths. - Backslashes are not valid as separators. When reading catalog paths (either from a definition file or from the UI when creating/renaming catalogs) they should be normalized. When loading from file, leading and trailing slashes are already stripped. This task is for: - [ - [x] Replace `\` with `/` to accomodate Windows users. - [ - [x] Strip leading/trailing slashes when user inputs a path on the UI (i.e. via RNA setter).