"{PROJECT_FOLDER}" Does Not Resolve on macOS when Importing Scripts

[clevername27]

Pretty much that. (Work-around is to simply use the the script's name, and ensure the scripts are at the top level of your Scripts folder.)

[ustk]

@clevername27 Unless it's just a typo in the topic's name, it should be {PROJECT_FOLDER}
but if your script is in a sub folder it should just be include("mySubFolder/myScript.js");. there's no need for {PROJECT_FOLDER}

[clevername27]

@ustk Thank you for your response and the correction. (I've updated the title.) Yes, there are work-arounds, but it's a still a bug. Specifically, the scripts will load within HISE. and you can compile. The compiled plugin may work-partially. But not completely. I'm not complaining—the source code is available if I want to fix it. I'm simply posting this so other people don't spend two weeks trying to figure out what's going on in their own code. Thank you again for your response and suggestion.

[ustk]

@clevername27 I'm not 100% sure to understand. Where are your scripts located?

[clevername27]

@ustk Thank you for your question. They're in the Scripts folder.

[d.healey]

Same as this one I believe - https://forum.hise.audio/topic/4927/project_folder-for-includes?_=1673027391165

[ustk]

@clevername27 @d-healey But why would you use "{PROJECT_FOLDER}" anyway?
When you "Move selection to external file", Hise does not add it...

Well maybe it is just that you are used to add it for many things, but since I always create external files from the right click in the code editor, I never had the habit to see the project folder wildcard...

[d.healey]

@ustk

Well maybe it is just that you are used to add it for many things

This reason. And then once you've done it you don't realise your mistake until weeks later when you go to compile and nothing works :p