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

 

Hello,

if CVI (in my case: version 2017) starts up and does not find a source file, it displays a message popup saying that 'The file "xyz" was not found. The breakpoints and tags in it have been removed.'

This however seems not to be the case.

If one simply renames the source file, starts and quits CVI and then renames this file back to the original name and restarts CVI all breakpoints and tags are still there (fortunately).

0 Kudos
Message 1 of 18
(3,237 Views)

Hello Wolfgang,

 

the breakpoints are stored in the cws file. So what do you do with the workspace file in this issue? Do you remove it or do you open it? Additionally, where do you rename the source file? In CVI or in Windows Explorer?

 

Best,

Melanie

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

Hi Melanie,

I don't touch the cws file. For testing I simply renamed the source file in Windows Explorer, started CVI, saw its warning message and quit CVI. Afterwards I renamed my source file back to its original name, started CVI again and was happy that everything was fine, i.e., that no tag and no breakpoint had been removed.

So I think that everything is fine except the (misleading / wrong) popup message.

0 Kudos
Message 3 of 18
(3,182 Views)

Hi Wolfgang,

 

I tried to reproduce the issue you see on my machine with CVI 2017. I did:

 

Creating a source file, project and workspace.

I added some code to the source and set a breakpoint. I saved all files.

Then I quit everything and rename my source (bp => bp_).

I open the source and see the message you descripted before.

I close CVI and rename the source back (bp_ => bp).

I open the source and get the file not found dialog again, this time without the breakpoints hint, because there are no breakpoints anymore. Why? At the point I open the cws file with the "wrong" source file name, the original file name entry is removed and with it the breakpoints are. So in my case I see everything as expected.

 

I have an idea, why you might get the breakpoints back. If you open the source after renaming and it is opened in a workspace different than the one you saved it in, you might not loose the breakpoints, as long as original cws is not touched.

 

Does that help you?

Best,

Melanie

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

Dear Melanie,

Thanks for your interest and efforts!

Basically I do it the same way, let me just clarify a few issues:

- I start with an existing project (several c, several h, one uir, one prj, one cws). Start means, I click on the CVI desktop icon. All files and breakpoints are there.

- I quit CVI and rename the first source code file as you by adding an underscore using Windows Explorer.

- I click on the CVI desktop icon and receive the warning message, indeed the file has disappeared from my tab list, and the editor now shows a different file.

- I quit CVI and notice that the date modifed of the cws file has been changed to the current time.

- I rename the source code file back to its original name, and click on the CVI desktop icon. No more warning message but all files and breakpoints are there.

According to this procedure I assume that I always open the very same cws file, which is also reflected in the modified date / time value.

 

Below you find the entry of the respective source file within the cws file, this entry does not change, it looks the same after I have renamed the source file and received the warning.

 

Thanks....

 

Spoiler
[File 0002]
Path = "/c/Users/Wolfgang/Documents/CVI/xxx/xxx_main.c"
File Type = "CSource"
Disk Date = 3569902353
In Projects = "1,"
Window Top = 32
Window Left = 10
Window Z-Order = 1
Source Window State = "1,14072,14073,14072,0,0,0,0,0,141,0,0,0,0,0,78,1655,0,1694,0,349,683,1,0,"
Breakpoint 0001 = "1695,0,enabled,"
Breakpoint 0002 = "13187,0,enabled,"
Breakpoint 0003 = "23857,0,enabled,"
Line Tags Line0001 = "1346,1392,1418,1480,1501,1546,1568,1844,1875,1941,1983,2025,2065,2095,2125,2155,"
Line Tags Line0002 = "2185,2215,2245,2275,2304,2335,2372,2420,2452,2485,2539,2593,2668,2707,2772,2798,"
Line Tags Line0003 = "2830,2863,3170,3214,3345,4029,4059,4104,4157,4205,4312,4344,4372,4458,4489,4521,"
Line Tags Line0004 = "4553,4585,4617,4642,4674,4698,4729,4753,4783,4810,4833,4860,4891,4922,4953,4977,"
Line Tags Line0005 = "5008,5032,5063,5094,5125,5157,5182,5204,5234,5408,6141,6281,6326,6373,6429,6869,"
Line Tags Line0006 = "6969,7013,7100,7134,7183,7240,7298,7350,7380,7411,7441,7497,7522,7660,7851,7924,"
Line Tags Line0007 = "7967,8012,8039,8072,8098,8119,8224,8271,8382,9021,9047,9077,9108,9137,9168,9201,"
Line Tags Line0008 = "9264,9294,9325,9354,9387,9445,9500,9533,9559,9602,9645,9678,9720,9904,9964,10026"
Line Tags Line0009 = ",10053,10080,10107,10294,10321,10431,10458,10484,10543,10746,10771,11509,11691,1"
Line Tags Line0010 = "1717,11775,11805,11835,11865,11895,11925,11955,11985,12015,12045,12075,12105,121"
Line Tags Line0011 = "35,12164,12195,12761,12865,12896,12935,12982,13007,13031,13068,13105,13142,13179"
Line Tags Line0012 = ",13218,13303,13350,13375,13420,13451,13490,13537,13562,13607,13637,13675,13722,1"
Line Tags Line0013 = "3747,13790,13812,13834,13857,13884,13910,13940,13969,13996,14027,14119,14150,142"
Line Tags Line0014 = "22,14294,14324,14354,14383,14416,14623,14649,14675,14716,14741,14766,14789,14819"
Line Tags Line0015 = ",14849,14916,14945,14978,15039,15149,15704,15743,15948,16518,16552,16583,16617,1"
Line Tags Line0016 = "6664,16750,17492,17892,17980,18146,18262,18582,18745,18860,19069,19159,19394,194"
Line Tags Line0017 = "26,19487,19515,19561,19615,19639,19675,19717,19741,19777,20049,20072,20093,20115"
Line Tags Line0018 = ",20146,20264,20355,20377,20398,20421,20452,20480,20510,20540,20569,20645,20769,2"
Line Tags Line0019 = "0943,21024,21160,21204,21237,21331,21524,21610,21721,21755,21789,21823,21906,219"
Line Tags Line0020 = "68,22046,22085,22110,22135,22161,22186,22211,22236,22262,22296,22361,28795,28824"
Line Tags Line0021 = ",28853,28881,28909,29128,29157,29188,29240,29267,29296,29326,29363,30674,"

 

0 Kudos
Message 5 of 18
(3,167 Views)

Hi Wolfgang,

 

I played around with my project a bit and do not really get the behavior you see. One major difference is in fact, that I use a small project with just one source file. In general I would not expect anything different so far for larger or smaller project.

 

But to ensure we see the same behavior, can you check the behavior on your machine with a small project?

 

I watched my cws file when executing your steps. Anytime I close CVI and the cws is saved due to changes (source file has a different name), the old entry is removed in my case. Is that the same behavior as you see in the cws file?

 

Best,

Melanie

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

Hi MelanieE,

Thanks for coming back.

I will try as suggested and also take my project to another computer to see if I will observe the same behavior there as well.

0 Kudos
Message 7 of 18
(3,146 Views)

Hi again,

- I tried my project on a different computer with the result described by me earlier

- I tried one of the simple sample projects with one uir and one c file, CVI2017\samples\newexamples.cws which actually is TabExample.c in directory userint. I set a breakpoint in line 67, the cws file reflects this as

Breakpoint 0001 = "67,0,enabled,"
Renaming then TabExample.c to TabExample_.c yields the well-known warning, but the cws file still contains this line after quitting. So renaming the c file back everything is as before, i.e., the breakpoint still exists

0 Kudos
Message 8 of 18
(3,074 Views)

I cannot argue on this item since I'm not using 2017 yet, but I wonder if the different behaviour you two are observing may depend on the File >> Auto Save Workspace option being checked or not (this option is present in every version at least from cvi2009 on, so I suppose it'll be in 2017 too).



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 9 of 18
(3,032 Views)

Hi Roberto,

in my case this option is set. I am not sure if this is a CVI2017 feature, maybe it was like this before...

0 Kudos
Message 10 of 18
(3,026 Views)