From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Darren's Occasional Nugget 08/11/2008

Thanx for posting the screen shot of your block diagram darren.
Message 11 of 34
(7,425 Views)
> Off to the left of the diagram (not shown) is the private functionality I
was talking about.  Basically, I have to get all the Application
Instances where you might have VIs running...unfortunately, I don't think
there's a way to do this without private VI Server properties.

But if you are working one a project, there will only be VI's running in
your current application instances. So simply getting all VI's in memory
will do in most cases. At least it has been working for me. (I do a lot of
scripting, but never found the need to change my stop all VI).

Also, I simply stop all top level vi's. Guess it's a 'poor mans' solution.
(If I'd make my stop all VI more flexible, I'll never learn not to make VI's
modal untill testing is done.)

Another great use for VI's like this is to stop dynamic VI's started with VI
server.

Regards,

Wiebe.


Message 12 of 34
(7,385 Views)

VI is going to come in VERY handy, Thanks!

0 Kudos
Message 13 of 34
(7,252 Views)

Darren,

 

could you add the LabVIEW Dialog context as well

(I try debugging some IDE extensions)

 

Ton

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!
Message 14 of 34
(7,249 Views)

The utility I posted will parse the user's project context(s) and the Main Application Instance.  I cannot post a utility that will go through private contexts as well.

 

-D

Message 15 of 34
(7,245 Views)

See my post if you just want to change a modal dialog back to default - rather than abort.... I was inspired by this idea.

here

0 Kudos
Message 16 of 34
(7,030 Views)

HI

 

        Thanks for the VI.I have been to the situtions many times to end Labview .exe process. Its very useful and helps a lot!!!!!!!

0 Kudos
Message 17 of 34
(7,018 Views)

We appreciate for the efforts on "Abort VI.vi", recently I faced a problem where the "Statechart - Edit Triggers and Groups" window stops working and we could not close VI's. The alternative is to end the task from windows.The Abort VI.vi also could not stop this.

Manish Soni

0 Kudos
Message 18 of 34
(6,854 Views)

ManishSoni wrote:

We appreciate for the efforts on "Abort VI.vi", recently I faced a problem where the "Statechart - Edit Triggers and Groups" window stops working and we could not close VI's. The alternative is to end the task from windows.The Abort VI.vi also could not stop this.

Manish Soni


If you can reproduce this problem, please let us know. We would be eager to investigate it.

0 Kudos
Message 19 of 34
(6,836 Views)

Here is an unlocked version that only searches the current application instance..  I believe it was created by Dan Gilmore and offered on info-labview.  This version will search for all the modal vis and give a menu to close.

 

I always keep a version in my Dock to get out of self inflicted problems!!

 

Enjoy, and modify away.

-Scott

 

 Stupid Freaking Lithium, doesn't allow adding VIs as attachments.  Sheesh.

Here it is as a zip file.  I hear that works sometimes.

 

Message Edited by sth on 02-16-2009 03:40 PM

LabVIEW ChampionLabVIEW Channel Wires

Message 20 of 34
(6,537 Views)