Requested access. Low tech solution, but if it's just autowatch that is resulting in problems you could maybe use [filewatch] object and then call compile on your js again.

Sorry for the restricted sharing, my Google Drive link should work now. Thank you for the filewatch idea, I'll have a look !

I've done some more tests this morning and I start to think the problem is not due to the autowatch option. Actually, if I edit let's say a string in one of my debug post(), the new string appears as expected in Max console after saving the JS files and initing my M4L device. So I'm pretty sure my JS files are recompiled as expected. The 'history' 'ghost' outputs I get with my code in Max console seems to be in relation with the variable returned by the require() function itself. Apparently require() returns a jsobject, and when I debug it I get a negative value, I guess it's a kind of pointer or address. It looks like a new 'pointer' is created by require() each time I run my code, and that the previous 'pointers' are still active in memory. So their onParameterChange() function may still be active too, which could explain the 'history' output I get. Am I right ? Is there a way to notify the garbage collector to delete these plausible 'previous pointers' ? I don't know how I can inspect the variable returned by require() a bit more. I know that a getprop() function exists for jsobject, but I don't know what to pass as arguments to get info from the variable... An idea ?

This is a limitation/bug in the current implementation of jsrequire. We're looking into it, thanks for bringing it to our attention!

Hi Jeremy, Great ! I'm happy you've found the problem with JS require. While an improvement is under study, I will rename my main js patcher each time I'll have to edit my JS subcode, it seems to avoid the problem of multiple ghost outputs from JS require. Cheers. Guillaume

Guillaume,

I'm doing nearly the same thing you have described. I'm writing an editor for a hardware synth. I have three .js files: one that handles interaction with the synth, one that defines the dictionary of params for the synth, and one that interacts with the UI controls.

I've put post("loaded module v0.1 \n") commands at the top of each .js script. Even though the updated version number in the top line shows up properly in the console when I save, the function I am working on fails to recompile, and my edits are ignored.

I have to close the project and reload it for my edits to be seen.

Rick

Hi Rick, What Max version do you use ? I encountered this issue while I was developing under Max 8.1.7. I've reported the problem to Jeremy @C'74 (see older posts above), and normally the bug has been resolved since then. Have you tried to double click on the name of your main JS patcher, like if you would like to rename it, and then press enter ? This trick seems to force the autowatch mecanism and should help you to reload the last versions of your edited JS patchers. Guillaume

Guillaume,

Thanks for the speedy reply! I was using 8.1.8. I've now installed 8.1.10 and the problem persists.

I tried your suggestion to double-click the name of my main JS patcher. That didn't work, but it led me to try closing only the patcher (instead of the project), then reloading with the double-click on the main patcher in the Project window. That caused the .js to be properly reloaded.

The thing that has me scratching my head is that the autowatch appears to be working (at least partially). That is, in the main body of the .js updated post() commands are reflected in the console "automagically" when the file is saved. That led to me believe that autowatch was working. The problem is that functions within the .js are not reloaded, and fail to produce updated post() commands.

Thanks again,

Rick

You're welcome Rick :)