LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI Snippet bug

Solved!
Go to solution

I was trying to use the new LabVIEW 2009 VI snippet tool and got one semi serious problem, and one serious bug.

I tried to get this snippet right.

First problem was that the VI must be save before 'Snipping'.

Second is taht when I tried to capture the event frame I got a series of dialog stating that I sould report it to NI tech personel.

Third is that  the whole VI was captured.

 

In the attachment (temp.zip) is the XControl that created this (LabVIEW 2009), I have reproduced this even after a LV restart.

I only tried to capture the event structure inside the facade VI.

 

Ton

 

PS I am serious not just to diss the snippet tool

 

 

Message Edited by TonP on 08-05-2009 01:35 PM
Message Edited by TonP on 08-05-2009 01:38 PM
Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Download All
Message 1 of 5
(3,486 Views)
Solution
Accepted by topic author TCPlomp

Hello Ton,

 

thank you so much for your post. I created a new XControl and was able to reproduce it. It looks like it has something to do with the events that are used in the events structure (like direction change). I will file this problem.

 

Best regards,

Martijn S
Applications Engineer
NI Netherlands
Message 2 of 5
(3,393 Views)

This was reported to R&D (CAR # 182002) for further investigation.

 

Roy

0 Kudos
Message 3 of 5
(3,353 Views)

Hi Roy,

 

one more problem with snippet creation...

 

See attached vi and according snippet.png. In the snippet the content of a [array of] cluster constant is invisible - which is rather annoying when that is just the main part of an example...

Message Edited by GerdW on 09-12-2009 05:49 PM
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
Download All
Message 4 of 5
(3,226 Views)

Hello GerdW,

 

the cluster is coming visible again when placing the cluster back into the block diagram. I noticed a Corrective Action Request which explains the same problem; it looks like the elements within the cluster are shifted. This CAR (# 184059) is already under investigation.

 

Thank you so much for bringing this problem up,

 

Best regards,

Martijn S
Applications Engineer
NI Netherlands
Message 5 of 5
(3,184 Views)