I recently posted about the Fusion API Webinar and want to correct and clarify a few things I said during the presentation and in the questions after.
- When showing the slides comparing the JavaScript and Python code I mentioned that JavaScript is pickier about types and sometimes requires type casting. This is not true. There was an issue in a very early version of the API where it did require type casting but that was a Fusion API issue and not a JavaScript issue and has long since been addressed. I’ve updated the PowerPoint slides to remove the casting line.
- It was asked if you could begin a debug session into a running JavaScript add-in and replied that I didn’t believe it was possible. I’ve since learned about a capability that I didn’t know about that does allow you to debug into a running JavaScript add-in or script. From the Scripts and Add-Ins dialog you can see which scripts and add-ins are currently running by looking for the running symbol next to the name as I’ve highlighted below. When you select a running JavaScript program, the Debug button will be enabled, as shown below. This will open a window and allow you to begin debugging the running script.
- I also mentioned TkInter as a way to create custom dialogs when using Python but that there are currently problems when using it on a Mac. This is true but I want to clarify that it’s not a Fusion 360 API issue in this case but is a general problem with TkInter (Tcl/Tk specifically) on Mac. We’ve attempted to find a combination of libraries that works but so far have been unsuccessful.
<p>-Brian
Leave a Reply