New Bug in CVI2013SP1?

[ebalci]

I wonder if enabling/disabling "Embed UIR file into executable" setting makes any difference?

Normally, if enabled, changing the uir reqires a rebuild.

[Wolfgang]

Hi Eren,

I do have "Embed project .UIR's" enabled. However, if I change the UIR file, save it and only then press the green triangle there is no recompilation... but the executable shows the modified UI...

[ebalci]

It is logical that it does not recompile. It should just add the new uir resource to the readily built binary.
The difference might be in the include file associated with the uir.

If the uir change requires a change in the header, the source files including that header have to be recompiled. Otherwise I think it is a simple appending operation to embed uir into exe.

Maybe if you save it first, it can realize if the change effect the header or not. If you run it directly, maybe it rewrites the header anyway and therefor recompiles the files including that header.

Can you try making a more radical change, like changing the tab order (this causes the IDs to change) and save by clicking the toolbar.
The source files that include the header should get marked for compilation.

[Wolfgang]

Hi Eren, thanks...

I have tried your suggestion and you were right: adding a new control, for example, forces a compilation in both cases (as expected).

So my initial question remains why the two approaches to compile a project after a 'small' change of the UIR behave differently, or, as Eren called it, why is pressing the Save disk icon smarter... in my opinion both user actions should yield the same program action

---

@ebalci wrote:

Maybe if you save it first, it can realize if the change effect the header or not. If you run it directly, maybe it rewrites the header anyway and therefor recompiles the files including that header.

---

"Maybe if..." It would be nice to hear from NI what actually is happening so that we don't have to guess

[Constantin--P]

Hello Wolfgang,

Eren is right. When saving the *uir the associated header file is not modified if not necessary. But if you click Run without saving the file the header file is re-written. You can see this if you look at the timestamp of the h file.

I think what this dialog displays: "Saving them will cause CVI to generate new versions of their associated include files." wants to suggest this behaviour but I'm not sure.

Why are you saying this is a new bug in CVI2013SP1? I can see the same behavour in the earlier versions.

Thanks,

Constantin

[Wolfgang]

---

@Constantin--P wrote:

Hello Wolfgang,

Eren is right. When saving the *uir the associated header file is not modified if not necessary. But if you click Run without saving the file the header file is re-written.

Why are you saying this is a new bug in CVI2013SP1? I can see the same behavour in the earlier versions.

---

Thanks Constantin for confirmation!

The reason I called this behavior new simply was that I did not remember to have seen this before

[Wolfgang]

---

@Constantin--P wrote:

Why are you saying this is a new bug in CVI2013SP1? I can see the same behavour in the earlier versions.

---

My focus was not so much on the 'new' 😉

So Constantin, would you agree that this behaviour is 'counter-intuitive' and deserves a CAR?

[Constantin--P · Accepted solution]

Hello Wolfgang,

The CAR number is 464163.

Have a nice day,

Constantin

[Wolfgang]

Thanks!

[Wolfgang · Accepted solution]

fixed in CVI 2020