- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
While waiting for some new inspiring* info I managed to create an inelegant workaround for the Case#1 based on assumption that all I need is the 2nd code run.
Now I run the Core-code (an external iLogic rule) with another "Wrapper" iLogic rule TWICE.
1-st run processes the 1-st FOR-cycle iteration and returns index of the item it failed on.
2-nd run starts from the point of the fail.
Thus at least I get things done with running code (wrapper-rule) just once.
Those interested can find result of my coding together with a sample part (Inventor 2022 and STP export for earlier versions) in the ZIP attached.
Yet I don't feel happy - I still need some official comment on this issue from some competent Autodesk person .. because it looks like ... an Inventor API defect, right?
* I was told that the issue (apart from iLogic) is reproducible in VBA and updating to Inventor 2023 doesn't solve it either.
I have no plans to re-check those statements myself yet I'm going to try to reproduce it in C#.
Please vote for Inventor-Idea Text Search within Option Names