LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
gksloane

CTRL-SHIFT-Run should display progress windows the same as MASS COMPILE.

Status: New

When you mass compiled, all VIs in the directory tree get recompiled. When you hold CTRL and SHIFT and click the run button on a VI, it forces a recompile of all VIs in the call chain. 

 

However, when you CTRL-SHIFT-Run, all you SEE is a busy mouse; it would be really nice if you could get a popup windows (the same as when you mass compile) showing what's going on, and giving options to cancel... it would also be nice to be able to specify a log file and how many VIs to cache, same as with mass compile...

 

It could be the same popup with a different title...

 

 

15 Comments
wiebe@CARYA
Knight of NI

Not https://www.ni.com/pdf/manuals/373353d.pdf.. but https://www.ni.com/pdf/manuals/373353d.pdf (I did mark "open in new page", but it won't?).

 

This points to the LabVIEW Quick Reference Card. It seems more than just something someone mentions on the forum. It could still be just that, but it looks like an "official" NI Issued document. This might still not make it a documented feature...

Hooovahh
Proven Zealot

I'm pretty sure I got a reference card like that with a purchase of LabVIEW a few years ago, back when NI shipped optical media in a box. I'll try to avoid CTRL+SHIFT+R, but that is a pretty official release to me.

User002
Not applicable

I also found "Ctrl+Run button" and "Ctrl+Shift+Run button" here:

https://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/keyboard_shortcuts/

 

At least the link that wiebe@CARYA posted, https://www.ni.com/pdf/manuals/373353d.pdf, is copyright 2010 and has the word "Archived:" in the webpage title...

 

Regardless, @AristosQueue (NI), thanks for informing us that it's private functionality.

 

-joeorbob

ogrant
Member

ctrl + shift + run is one of those tools I have to use on a frequent basis, where a mass compile and other techniques fail to fix an issue, ctrl + shift + run finally gets the job done.  It is also frequently mentioned in the build window when a build specification fails.  

wiebe@CARYA
Knight of NI

In 21 years, I don't think I ever needed it. Tried it a few times, and it didn't help anyway.

 

I must be doing something right, or you're doing something wrong. Or maybe it's just my luck of certain hardware\software I'm not using? Perhaps I just found more creative ways to fix problems?