- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi Adam,
It would be difficult to provide any non-confidential example model here, but our company has a support agreement with Autodesk, and we have an Autodesk implementation consultant with whom we may be able to work something out. I will try to get in touch with him.
Both Update() and Update2() result in the same behavior. I'm using Update2() to provide the "accept errors and continue" option. It's probably worthy of noting that other API calls prior to Update2() also cause Inventor to appear busy while my program is ready to proceed to other calls... it isn't only Update2(). But Update2() seems to be the only one that, if another call is made before Inventor is "done", throws an exception and crashes Inventor. The calls made before Update2() are: OccurrencePattern.Delete(), ComponentOccurrence.Delete(), and BrowserFolder.Delete().
If this turns out to be an issue then maybe placing your code inside a command, running that synchronously, and then waiting for the OnTerminateCommand() event to run the SaveAs part might be a workaround. We'll see.
I'm unsure what you mean by this, and I suspect that "placing [our] code inside a command" isn't something I've done with the API before. It sounds at least somewhat promising. Could you link to more information about this? (When I refer to "executing an API command", I mean only executing a line of code that accesses the Inventor API.)