New Bug in CVI2013SP1??

[JaydenLouis]

In CVI2013 there was a bug (bug id 433769) when changing the uir file: the change did not show up, one needed to rebuild the project, this seems to have been fixed, but now there is something else... 

I have a project with several source files and one UIR file. All source files are compiled, so when pressing the green triangle button the project starts immediately, i.e. the only message shown in the Build Output window is Build succeeded.

Now I change one attribute in the UIR file (say the panel title).

Scenario A: After modifying my UIR I press the 'save disk' symbol to save the uir file, and only then press the green triangle button. The build action taken is Linking the project, and the program shows the correct UIR. So this is fine.

Scenario B: After modifying my UIR I press the green triangle button, CVI then prompts me that the UIR has been modified and needs to be saved. Pressing the OK button then is very time consuming because in this case CVI recompiles all source files, links them, i.e. it seems to perform a complete rebuild... This I would consider a waste of my time and not as expected

Well, there is a workaround (scenario A), but I suggest to include a fix in SP2

[RobertoBozzolo]

The warn about file(s) to be saved before running the project are probably due to an IDE option you have in your CVI install: go to Options >> Environment... dialog and check that both Save changes before compiling and Save changes before running are set to "Always": this will make CVI automatically save unsaved files before running the project.

Having said this, it is true that when CVI saves the UIR on Shift-F5 (Debug project, equivalent to the green-triangle button) it will compile all the sources that are using the UIR file it saves; this behavior nevertheless is consistent across multiple versions of CVI from at least 2012 and up to 2017 (I cannot test out of this range now), so this does not seems a "new" bug to me (and maybe not even a bug).

Besides that, you are not likely to have now a new SP for CVI2013 which is several versions older than the last one released.

[rolfk]

---

@JaydenLouis wrote:

Well, there is a workaround (scenario A), but I suggest to include a fix in SP2

---

As a principle rule NI does NOT release bug fixes for older versions than the latest currently shipping version of a software. There have been a few exceptions in the past when a VERY critical security bug fix got backported to a previous version, but what you report here does definitely not amount to a critical security bug and at best can be called an inconvenience.

2013 is a very old software version to still expect to get bug fixes for.