Replies: 4 comments
-
|
I just found Force Icon Editor to Unload.vi under Tooling, which appears to do the initial goal of this issue. I still think it would be good to make it optional to not keep the Icon Editor in memory to avoid the need to run this VI after every edit. |
Beta Was this translation helpful? Give feedback.
-
|
The second part might be solved by adding a new key to the LabVIEW.ini file. For example a key named "UnloadIconEditorFromMemoryWhenItCloses" could be read by the Icon Editor from LabVIEW.ini. On close, the Icon Editor would call the Force Icon Editor to Unload.vi if that setting has a value of "True". |
Beta Was this translation helpful? Give feedback.
-
|
My solution would be to just not run the Call Keep IE In Memory.vi based on whatever ini flag we make up. |
Beta Was this translation helpful? Give feedback.
-
|
@crossrulz it makes sense to me to turn this issue into a discussion, and then create issues referencing that. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
While making edits, we want to be able to test those updates. If LabVIEW is using the source, we are not able to test our updates as an older version is still in memory. We need a way to either unload the Icon Editor that is in memory or prevent LabVIEW from keeping it in memory.
Beta Was this translation helpful? Give feedback.
All reactions