LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

copying indicator causes force close during execution

I'm not sure if this action is frowned upon but when I need a new control or indicator I often copy and paste existing ones instead of dragging them from the pallete. Of course I rename the new ones. This has not presented a problem for me until this past weekend. I had made some minor changes to some code that included adding two additional charts. The new charts are identical to the existing ones except they get data from a different column of an array. After adding the charts the program would run for 2-3 minutes and force close Labview. After ~1 day of debugging I found that if I left the charts in question unwired the program ran fine. But wiring them up caused a crash.

 

I solved the problem by deleting the new charts and dragging new ones from the palette. Now the program does not crash.

 

Any comments? Is this a bug? Or bad programming on my part?

 

Thanks,

Dave

 

0 Kudos
Message 1 of 2
(2,225 Views)

I have read about an occational curpted control leading to a crash with the fix being to delete and replace it.

 

The other factor that could come into play is the "default" data for the chart.

 

If you found this in a recnet version of LV and you have backups from before the change and can recreate the crash, then by all means pass it along to NI so they can witness all of the glory of LV crumbling themselves and get it fixed of course.

 

Speaking only for myself, I do not find your method of copying a control bad at all. It is less time consuming than create custom controls which is what is recomended if you are dropping the same type of control often.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 2
(2,221 Views)