- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi @JamieVJohnson2,
Thanks for replying. I had thought of using the API to process each file in the working folder that contains a derived component, and in theory the code to do so is quite simple:
'Pseudo-code follows:
For Each File as Document in WorkingFolder
If TypeOf(File) is PartDocument then
Dim partDoc as PartDocument = File
If partDoc.Contains(DerivedComponent) then
Open PartDoc
Navigate Part Browser to DerivedComponentFeature
Run Edit Derived Component Command and wait for the user (me) to click okay
End if
End if
Next
This of course relies upon me finding the correct command using the Event Viewer.
And being able to navigate to the correct part feature in the browser before activating it.
One could argue that doing all this is likely to take longer than manually clicking through the 200 or so parts that I know for definite contain derived components, but I think it's probably worth it in the long-run as it'll mean that whoever picks up this project if I were to move on, (or if I have to migrate it again in future) the manual work is eliminated.
My OP was a "WTF Autodesk, should this happen?" observation as well as a cry for assistance that hopefully help myself/others in future. (By way of a patch being produced or a comprehensive workaround that doesn't involve countless hours of "Open offending part, edit derived-component, click okay")
Thanks,
Alex.
Alex Fielder
Inventor Expert
https://github.com/alexfielder/
LinkedIn - Github Inventor Extension Server - Bonkers polygon iLogic thing
Top ten iLogic Tips - API Shortcut In Google Chrome - Assembly Extrusion Example