![]() This will cause the stop method to be called and any break points will be hit allowing you to debug the stop function. To stop an add-in in a controlled way, you can switch back to Fusion and from the "Scripts and Add-Ins" dialog, choose the add-in and click "Stop". Typically, the stop function removes any user-interface items the add-in added when it was loaded. When an add-in is stopped using the "Stop" button in the "Script and Add-Ins Dialog", Fusion calls the add-in's stop method to allow it to clean up before it's unloaded. Any break points in the command created event handler will now be hit and you can debug the command execution. Switch to Fusion and run the add-in command. Starting to debug the add-in will execute the run method and then appear to be done but the add-in is still running but waiting to respond to an event which is typically the execution of one of its commands. Typically an add-in will create it's user-interface and connect to events in the run method and then run in the background waiting for an event to fire. Fusion loads the add-in and calls the run method, just like it does for scripts. Start debugging the add-in from within VS Code the same way as you would debug a script.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |