Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unique circumstance where .js file will not re-instantiate when saved #22

Closed
michaelpalumbo opened this issue Oct 31, 2019 · 2 comments
Closed

Comments

@michaelpalumbo
Copy link

Hi there. I created a .js script for prototype, verified it would reinstantiate in rack whenever i saved changed to the js script. I built a patch around it, saved the .vcv file in the same folder as the .js script. Then I zipped that folder and sent it to a friend. He was able to run the patch, but when he made changes to the .js code and saved it, it did not reinstantiate in vcv rack. I was able to reproduce this myself as well.

@AndrewBelt
Copy link
Member

This is expected behavior. Patches refer to scripts with absolute paths, using the embedded script string as a fallback. Your friend is using the fallback. He needs to load the script in VCV Prototype by navigating to the new location if he wants to make changes to it.

@michaelpalumbo
Copy link
Author

ah ok. thanks for this, i'll make sure notify him.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants