Open wireddown opened 6 years ago
I have to congratulate you on the detailed bug report.
You've pointed to a very important missing feature in the tool: transaction begin and undo. At this time, they are non-existent.
The SMO Editor is not part of this open-source project and is currently not published. I know that JKI's intent was to open source it as well so that the community can propose improvements. The code for the editor is not password protected, so it can de inspected and debugged. (If interested, the main VI is located at
The type of errors you are seeing looks like they are from disk permission errors. I am not well versed in LV for MacOS, so I'll let others chip in with comments. (I've never seen the sequence of errors you describe in the Windows version... although similar errors would probably produce similar results because of the absence of transaction wrappers.)
Regarding the editor: Do you personally use it Francois? A find it a little cumbersome to use even if I like the SMO framework a lot.
I have to admit that I don't use the SMO Editor in its current state. I personally always start from a blank object and inherit from SMO Base, then grow it manually. I spend way more time in the object architecture than in creating methods, so even though it is fastidious to repeat the same patterns by hand, I found that it still worked for me.
I heard that many people use openGDS to script their methods and accessors for SMO (and other frameworks).
The JKI SMO Editor removes the Typedefs from my SMO when I add a public method.
Usually, when a tool's operations on user data can fail, they can be rolled back by the tool. It would be helpful if these workflows were made transactional: apply-or-noop.
Add a public method
Error dialog
Empty Typedefs folder
Error text
Before / after projects
Software