Fusion
Hi @echatzief .
I think the reason for the error is that the process is executed too early.
I used this add-in to make the palette appear when Fusion360 is started.
https://github.com/kantoku-code/Fusion360_Developers_Small_ToolKit
The event I used is the UserInterface.workspaceActivated event.
And once the event occurs, I delete the handler that was registered.
https://help.autodesk.com/view/fusion360/ENU/?guid=GUID-fcb72832-b3bb-4a12-b590-977e75e915ca
The add-in over there is very voluminous, so I have created a minimal add-in and attached it for you to try.
The 'Hello World' dialog is displayed when an event occurs.
However, the timing of the event is here.
Depending on what you are processing, you may need to combine other events.
This is a meaningless add-in, but if you create this code as an add-in, check the "Run on Startup" checkbox, and start Fusion360, you can see the order in which events occur. The only condition is that you do not perform any operations.
# Fusion360API Python addin
import traceback
import adsk.core as core
handlers = []
def run(context):
try:
app: core.Application = core.Application.get()
ui: core.UserInterface = app.userInterface
global handlers
workspaceHandler = MyWorkspaceHandler()
handlers.append(workspaceHandler)
ui.workspaceActivated.add(workspaceHandler)
commandHandler = MyCommandHandler()
handlers.append(commandHandler)
ui.commandTerminated.add(commandHandler)
applicationHandler = MyApplicationHandler()
handlers.append(applicationHandler)
app.startupCompleted.add(applicationHandler)
documentHandler = MyDocumentHandler()
handlers.append(documentHandler)
app.documentCreated.add(documentHandler)
app.documentActivating.add(documentHandler)
except:
core.Application.get().log('Failed:\n{}'.format(traceback.format_exc()))
def stop(context):
try:
pass
except:
core.Application.get().log('Failed:\n{}'.format(traceback.format_exc()))
class MyDocumentHandler(core.DocumentEventHandler):
def __init__(self):
super().__init__()
def notify(self, args: core.DocumentEventArgs):
core.Application.get().log(f'{args.firingEvent.name}')
class MyApplicationHandler(core.ApplicationEventHandler):
def __init__(self):
super().__init__()
def notify(self, args: core.ApplicationEventArgs):
core.Application.get().log(f'{args.firingEvent.name}')
class MyWorkspaceHandler(core.WorkspaceEventHandler):
def __init__(self):
super().__init__()
def notify(self, args: core.WorkspaceEventArgs):
core.Application.get().log(f'{args.firingEvent.name}')
class MyCommandHandler(core.ApplicationCommandEventHandler):
def __init__(self):
super().__init__()
def notify(self, args: core.ApplicationCommandEventArgs):
core.Application.get().log(f'{args.firingEvent.name}')
In my environment, the result looks like this
StartupCompleted
DocumentCreated
DocumentActivating
OnWorkspaceActivated
OnCommandTerminated
OnCommandTerminated
OnCommandTerminated
The StartupCompleted event is fired before the DocumentCreated event when a new document is created at startup, and I feel that I cannot do anything with it.
This is why I chose the OnWorkspaceActivated event, because I just couldn't get it to work before.
If you think the slower the better, you might be better off using the OnCommandTerminated event, which is fired the first time.
Perhaps there is a more appropriate event.
The attached add-in uses threads to create a manufacturing setup and import a Step file at startup.
In a new document, I could not create a new setup this way.
I am not sure why, but if I had only one setup in an empty document, I could create it, so I imported the previously created document and imported the Step file as well.
I imported the template and tried to run the calculations, but Fusion360 crashed. (Ver 2.0.15509)
This is as far as I can help. I look forward to hearing back from you with good results.
I noticed that the documentation is publicly available.
I used Insider (Ver. 2.0.15775) and combined it with this sample.
https://help.autodesk.com/view/fusion360/ENU/?guid=GUID-c4836048-974e-4544-acc0-d384e7e55613
At startup, the creation of the setup and the creation of the operation succeeds, but,
When I run the generateToolpath method to calculate the toolpath,
Fusion360 crashes.
Running the sample script after Fusion360 starts works fine.
If I run Fusion360 while starting it up, it crashes, but if I run it after startup, it runs correctly without crashing.
Perhaps it is a timing issue and not a bug.
