LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Crash LabVIEW in one click

The buggiest LabVIEW ever (8.6.1f1) keeps on giving:

 

WARNING: will crash LabVIEW and you will lose any unsaved work. 

 

 Open the INFO CLUSTER ctl in the attached LLB (28kB).

 

(Yes, I know it's ugly, I'm trying to work on it)

 

Right-click on the table.

 

Watch LabVIEW die.

 

Arrrgh. 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 1 of 7
(3,344 Views)

I beg to differ, LV 8.20 was the buggiest LV ever. :smileytongue:

 

If you tried to use LVOOP that is.

 

Shane.

0 Kudos
Message 2 of 7
(3,340 Views)
It crashed on LV 8.6.0 as well.  Actually appears to be a Windows crash rather than a LV crash.
0 Kudos
Message 3 of 7
(3,293 Views)

I can open it on my Mac in LV 8.6.0.

 

It has some serious overlap issues in the lower right hand portion.  (And that is ignoring the common font size issues seen when changing platforms).

 

Is there something you know needs to be fixed so you can use it?  Perhaps I could do it for you and post the modified version here.

 

Lynn

 

Crash cluster.png

0 Kudos
Message 4 of 7
(3,269 Views)

Yes, I know about the overlap stuff.

 

Like I said, I was working on it and re-arranging stuff on the page when I discovered the bug.

 

Actually, I worked around it like this:

 

Copied the MCListBox to a blank VI.

Created a generic property node.

Linked the property node to the MCListBox.

Set the AUTOSIZE ROW height false

Set all the row heights to 23 instead of 25.

Pasted the copy in place of the original in the control I was working on. 

 

That's what I wanted to do via dialogs, but crashed instead.

 

Thanks for your offer, though. 

Steve Bird
Culverson Software - Elegant software that is a pleasure to use.
Culverson.com


LinkedIn

Blog for (mostly LabVIEW) programmers: Tips And Tricks

0 Kudos
Message 5 of 7
(3,260 Views)

Steve,

 

OK.  Glad you found a work around.

 

Lynn 

0 Kudos
Message 6 of 7
(3,238 Views)

Hi Everyone,

 

This issue has been reported to R&D for further investigation as Corrective Actio Requeset (CAR) #179492. Thanks for the feedback!

Joshua B.
National Instruments
0 Kudos
Message 7 of 7
(3,160 Views)