LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Misleading warning on CVI startup: breakpoints and tags have been removed

Solved!
Go to solution

Just tested in 2015 with a shipping example; breakpoints and tags are not cleared from the .cws after openint the project with a missing file. I see your same behaviour: breakpoint and tags are retained and represented the next time I open CVI with the file present again; I am also warned that they will be cleared, even if they aren't.

I have the Auto Save option set, too.

 

It is to be said, though, that if I make some modification that implies saving the workspace (e.g. open a new file or close an opened one) taks and breakpoint are cleared, even it the missing file section is still present; reopening the workspace with the file present again will result in breakpoints and tags cleared in that file.

 

So it seems the warning is not fully misleading: only if no modifications at all are made breakpoints and tags remain in the project, otherwise they are cleared.



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
0 Kudos
Message 11 of 18
(1,249 Views)

Thanks for confirmation, Roberto.

0 Kudos
Message 12 of 18
(1,243 Views)

Hello MelanieE,

 

what about a win-win situation: you provide us a CAR and and talk to your colleague to have it implemented today (before we forget), I provide the solution which seems pretty simple to me:

All that is needed from my point of view is changing the text of the warning pop-up message, from

 

The file "xyz" was not found. The breakpoints and tags in it have been removed.

 

to

 

The file "xyz" was not found. If now you make changes to your project the breakpoints and tags of file "xyz" will be removed.

 

I think that the latter statement correctly describes the current behavior of CVI.

0 Kudos
Message 13 of 18
(1,219 Views)

Hi Wolfgang,

 

I have not been in office for a while, so sorry for the delay.

 

I think we have some new points here I need to check on my machine. Give me some time for it, I will update you, if I see the same behavior. If so, we can continue with your win-win sugestion.

 

Best,

Melanie

Best regards,
Melanie Eisfeld
Senior Applications Engineer, National Instruments Germany
Certified LabVIEW Developer
Certified TestStand Architect
0 Kudos
Message 14 of 18
(1,188 Views)

Hi Melanie,

everyone is permitted vacations Smiley Happy I will be ooo in September Smiley Very Happy So take your time and thanks for coming back!

0 Kudos
Message 15 of 18
(1,185 Views)
Solution
Accepted by Wolfgang

Hi Wolfgang and Roberto,

 

I played around with my project a bit more. With the discription from Roberto I was able to see the same behavior as you discribed, Wolfgang.

 

I will document the behavior the next days and post the ticket number.

 

Best,

Melanie

Best regards,
Melanie Eisfeld
Senior Applications Engineer, National Instruments Germany
Certified LabVIEW Developer
Certified TestStand Architect
0 Kudos
Message 16 of 18
(1,127 Views)

Hi Wolfgang and Roberto,

 

I reported the behavior today. The tracking number is: 665361

 

Best,

Melanie

Best regards,
Melanie Eisfeld
Senior Applications Engineer, National Instruments Germany
Certified LabVIEW Developer
Certified TestStand Architect
0 Kudos
Message 17 of 18
(1,118 Views)

Thanks Smiley Happy

0 Kudos
Message 18 of 18
(1,051 Views)