Inventor iLogic, Macros, AddIns & Apprentice Forum. Share your knowledge, ask questions, and explore popular Inventor topics related to programming, creating add-ins, macros, working with the API or creating iLogic tools.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
Apprentice ExecuteSave bug with suppressed parts in assembly
There possibly is a bug in the "ExecuteSave" function of Apprentice.
When we save an assembly with Apprentice (with VBA in Excel), and the assembly contains suppressed parts, Apprentice will exchange apparently random parts with other parts in the assembly.
For saving (with VBA in Excel) we use "FileSaveAs.AddFileToSave()" and "FileSaveAs.ExecuteSave".
Apprentice ExecuteSave bug with suppressed parts in assembly
There possibly is a bug in the "ExecuteSave" function of Apprentice.
When we save an assembly with Apprentice (with VBA in Excel), and the assembly contains suppressed parts, Apprentice will exchange apparently random parts with other parts in the assembly.
For saving (with VBA in Excel) we use "FileSaveAs.AddFileToSave()" and "FileSaveAs.ExecuteSave".
Today I tried to make a few images to visualize the issue, but I can no longer reproduce the bug.
Yesterday I still could reproduce it with different assembly's so I decided to make this forum post. Copying designs with our copy-tool is an important part of our workflow, we have to be able to trust the copy's that are being made with it.
Maybe it was a freak incident and it will never happen again...
Today I tried to make a few images to visualize the issue, but I can no longer reproduce the bug.
Yesterday I still could reproduce it with different assembly's so I decided to make this forum post. Copying designs with our copy-tool is an important part of our workflow, we have to be able to trust the copy's that are being made with it.
Maybe it was a freak incident and it will never happen again...
