[Relative path for resources (Feature Request)]

Hello,
impossible to integrate this software into a corporate workflow (with git, svn or teams file server) without two features:
  - the relative paths for the resource files (we are in 2022 damn it at the end!)
  - the filename variables in the exports (impossible to generate templates if the export cannot be dependent on the filename)

thanks to Serif for correcting his absurd policy of pushing us back to competition!

[Relative paths in resource manager]

Hello,
impossible to integrate this software into a corporate workflow (with git, svn or teams file server) without two features:
  - the relative paths for the resource files (we are in 2022 damn it at the end!)
  - the filename variables in the exports (impossible to generate templates if the export cannot be dependent on the filename)

thanks to Serif for correcting his absurd policy of pushing us back to competition!

[relative links vs. absolute paths feature STILL MISSING!]

Hello,
impossible to integrate this software into a corporate workflow (with git, svn or teams file server) without two features:
  - the relative paths for the resource files (we are in 2022 damn it at the end!)
  - the filename variables in the exports (impossible to generate templates if the export cannot be dependent on the filename)

thanks to Serif for correcting his absurd policy of pushing us back to competition!

[Add filename token to export slices]

 

hello,

This is a basic and indispensable component in a workflow! surprising that it is not there!

Exporting a XXXXXX file in XXXXXX_16x16, XXXXXX_dark, XXXXXX_light ... is a common action in our professions!