LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

delay when right clicking on a wire

I am experiencing a problem when right clicking on wires in my project.

 

Right clicking on any wire takes much longer(2-3 seconds) then right clicking on anything else.

 

When right clicking on VIs,VI connector panes, constants, structures, etc... the menu shows up almost instantly.

 

I tried right clicking on wires on a small VI with the project explorer open and with the project explorer closed (new VI with only a couple controls/indicators) and both have the same effect.

 

I noticed that, with the project open, when I right click on the wire, just before the menu shows up, some of my classes show the 'locked' symbol next to them then the symbol goes away.  It looks like its briefly locking my classes when I write click on any wire.

 

This only started happening a little while ago.  I've been using classes and this same project for a couple months now...but it just started causing a delay on right click.  Not sure what, if anything, I changed caused this....

 

Anyone have any ideas? This is super annoying and is slowing my development down like crazy.

 

Thanks,

Jonathan 

-----
LV 8.2/8.5/8.6 - WinXP
0 Kudos
Message 1 of 7
(3,499 Views)

Hi Jonathan,

 

Which version of LabVIEW are you seeing this in?  Have you been able to reproduce this on a different development machine with the same project?  Have you upgraded your LabVIEW recently?

 

If you have upgraded to a newer version of LabVIEW and are using custom probes?  If you are you should try mass compiling the project.  Even if you aren't, you might want to give it a shot.

 

Message Edited by Justin_P on 06-15-2009 12:29 PM
Justin Parker
National Instruments
Product Support Engineer
Message 2 of 7
(3,457 Views)
As Justin suggests, custom probes are the most likely cause. My guess is that you have custom probes saved on a network server that's not accessible.
Message 3 of 7
(3,432 Views)

Hi Justin, smercurio,

 

I am seeing this in LabVIEW 8.6, I haven't been able to reproduce this on another machine because I don't have access to 8.6 anywhere else.

 

I have not upgraded recently.

 

I was, however, experimenting with custom probes recently.  I tried using them for the first time a couple weeks ago, probably around the same time this started.  I don't think I saved any of the custom probes, but I need to look in to this.  I don't use a network server, all the development I am doing is on a laptop not connected to any other server.

 

Mass compiling does not seem to help any, as I have tried this a number of times.

 

Thanks for the responses, I'll see if I can find remenents of custom probes.

 

~Jonathan

-----
LV 8.2/8.5/8.6 - WinXP
0 Kudos
Message 4 of 7
(3,407 Views)

Ah HA!  I found a custom probe that I had saved that referenced a class.  I deleted the probe on disk, then mass compiled.  Clicking on the wires is now back to normal!

 

This is a very strange behavior...I'm not sure where the probe was placed...is there a way to lookup where it is? (used find callers to look it up, doh!)

 

I added the probe to the project, and then tried to place it in a few areas to reproduce the behavior.  I can't seem to get it to behave in the same way again.

 

Thanks!!

~Jonathan

Message Edited by malkier on 06-16-2009 06:07 PM
Message Edited by malkier on 06-16-2009 06:09 PM
-----
LV 8.2/8.5/8.6 - WinXP
0 Kudos
Message 5 of 7
(3,396 Views)

Ok, so the behavior seemed to come back after I removed the probe from the VI, removed the probe from the project, and mass-compiled the project.

 

I then deleted the probe from disk, mass compiled, closed and opened the project.  The behavior is now gone.  Is this a bug?

 

Let me know if there is anything I can do to test it.  I'll try to reproduce a smaller case test to post, but it might take me some time since I'm quite busy this week.

-----
LV 8.2/8.5/8.6 - WinXP
0 Kudos
Message 6 of 7
(3,390 Views)

Hi Jonathan,

 

This was reported to R&D (# 104160) for further investigation.  As Justin mentioned, and as you have seen, the delay is due to custom probes. 

 

Custom probes are stored at My Documents/LabVIEW Data/Probes, labview/vi.lib/_probes and labview/user.lib/_probes.  If you mass compile those three directories and delete unnecessary probes, you should see an improvement in the speed. 

 

Message Edited by Jennifer_R on 08-24-2009 05:10 PM
Jennifer R.
National Instruments
Applications Engineer
0 Kudos
Message 7 of 7
(3,290 Views)