ValliSoftware Posted January 24, 2018 Share Posted January 24, 2018 To cut down on my errors with Logic Pro X Scripters, I use Visual Studio 2017 to debug it. Using a debugger like Visual Studio helps me a lot. I show the template I use to debug a Logic Pro X Scripter object. Obviously, the final test is using Logic Pro X, but at least I'll cut down on dumb mistakes before going into Logic Pro X. Quote Link to comment Share on other sites More sharing options...
ValliSoftware Posted January 26, 2018 Author Share Posted January 26, 2018 So here's my setup. I put logic javascript to help in testing and debugging in logic.js. Then I put the simulation of Logic Pro X in main.js. In my index.html for the Visual Studio project, I just order these two files as well as a scripts/active.js entry. Anytime I want to work with a script in the scripts folder, I rename it to active.js and once I'm done, I rename it back to the original file name. This is working pretty good and very helpful in debugging Logic Pro X scripts. I'll see if I can get the same kind of setup with Visual Studio for the Mac since that's available now. js.zip Quote Link to comment Share on other sites More sharing options...
Eric Cardenas Posted January 26, 2018 Share Posted January 26, 2018 Thanks so much for sharing Valli. Quote Link to comment Share on other sites More sharing options...
ValliSoftware Posted February 2, 2018 Author Share Posted February 2, 2018 I finally got around to posting this on GitHub, search for the following: Logic-Pro-X-Scripter-Debugging I'm using the Visual Studio 2017 Community version. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.