As can be seen here, "Save changes" items in Environment options are global to the CVI IDE.
I suggest these options are made project-specific instead. The rationale behind this suggestion is simple: suppose I am developing project A and I enable autosave modifications before compiling and running the project; at the same time I may need to look at the code for project B already deployed to customers, and I want to prevent modifications to the code without notice. At present, while I am testing the application A I set these options to "Always"; if next I come and see the code for project B, I may accidentally make (and save!) modifications that change the code of the deployed app without notice
If these options were per-project I would be granted I am not making mistakes.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.