Jump to content

A very fast way to close your LabVIEW project


Jim Kring

Recommended Posts

Posted

Seems to work fine on other apps, too. Any reasons we should use this approach instead of just killing the desired process from Task Manager?

-D

Posted

QUOTE(Darren @ Oct 15 2007, 10:06 PM)

Any reasons we should use this approach instead of just killing the desired process from Task Manager?

Cause you can create a desktop shortcut for this ;)

Posted

QUOTE(Tomi Maila @ Oct 15 2007, 01:11 PM)

Cause you can create a desktop shortcut for this ;)

Yup. Actually, I created a .bat file, but a shortcut works very nicely, too :)

Posted

QUOTE(Jim Kring @ Oct 15 2007, 04:48 PM)

Yup. Actually, I created a .bat file, but a shortcut works very nicely, too :)

Now I need to create a vi with a blank icon and use a system exec call to that bat file and drive my co-workers crazy! :laugh:

Posted

QUOTE(Yen @ Oct 17 2007, 02:04 PM)

Maybe it's just me, but what's wrong with the various built in options (File>>Close All, Ctrl+Q, repeated Ctrl+Ws, etc.)?

This can take several minutes to close the Project Explorer, when you have a large project with lots of LVClasses. The more unsaved changes, the longer it takes (it even takes a long time with no unsaved changes).

Posted

QUOTE(Jim Kring @ Oct 17 2007, 11:17 PM)

This can take several minutes to close the Project Explorer

Oh, for some reason I don't seem to have that problem in LV 7.0. ;) :laugh:

Posted

QUOTE(Yen @ Oct 17 2007, 02:29 PM)

Oh, for some reason I don't seem to have that problem in LV 7.0. ;) :laugh:

Lately, it seems that the LabVIEW upgrade process is just trading problems. Get some new features and bugs fixed, but have deal with the new bugs. Granted, the new features are really nice, but it's pretty frustrating working around the new bugs and "inconveniences" (like waiting several minutes for your project to close or a typedef change to propagate). :headbang:

Posted

QUOTE(Jim Kring @ Oct 17 2007, 02:54 PM)

Lately, it seems that the LabVIEW upgrade process is just trading problems. Get some new features and bugs fixed, but have deal with the new bugs. Granted, the new features are really nice, but it's pretty frustrating working around the new bugs and "inconveniences" (like waiting several minutes for your project to close or a typedef change to propagate). :headbang:

<Warning Thread Hijack>

So true, and don't even get me started on the hierarchy windows which has become unusable since LV 8.0.

Used to be snappy and handy in 7.1, no longer the case...

</Warning Thread Hijack>

PJM

Posted

QUOTE(Jim Kring @ Oct 17 2007, 09:54 PM)

Lately, it seems that the LabVIEW upgrade process is just trading problems. Get some new features and bugs fixed, but have deal with the new bugs. Granted, the new features are really nice,...

I wonder how my eventual transition to 8.5 will be.

I have a fairly large "in house" project going in 8.2.1 and don't really have it fully sorted out yet in terms of Vi locations, etc.

I took a stab at loading it into LV85 and saw a lot of dialogs but did not have time to drill into it so I just closed it out for now.

Wondering if there is going to be an 8.5.1 patch coming..

Posted

QUOTE(TG @ Oct 18 2007, 03:03 AM)

Wondering if there is going to be an 8.5.1 patch coming..

In the LV User Group Meeting during VIP 2007 (last week's NI congress in Germany), the NI people told us that LV 8.5.1 will be released "in a couple of months".

Posted

QUOTE(silmaril @ Oct 18 2007, 04:46 AM)

In the LV User Group Meeting during VIP 2007 (last week's NI congress in Germany), the NI people told us that LV 8.5.1 will be released "in a couple of months".

Sure, and probably some time after that you will see LV 9.0. Oh and probably sometime after that you will see 9.1 then 9.1.1 then 10.0 then... So?

Posted

QUOTE(Michael_Aivaliotis @ Oct 18 2007, 07:38 PM)

and probably sometime after that you will see 9.1 ... then 10.0

Nah, that one would have to be LVX, wouldn't it?

Then maybe X.1?

Posted

QUOTE(Yen @ Oct 18 2007, 11:48 AM)

Nah, that one would have to be LVX, wouldn't it?

Then maybe X.1?

Maybe, but they won't be able to resist version 16 being LabVIEW XVI.

Posted

QUOTE(JDave @ Oct 18 2007, 03:24 PM)

Maybe, but they won't be able to resist version 16 being LabVIEW XVI.

They resisted for version VI. Instead we got the 6.0i. (Would that be VIi?)

Posted

QUOTE(Michael_Aivaliotis @ Oct 18 2007, 07:38 PM)

Sure, and probably some time after that you will see LV 9.0. Oh and probably sometime after that you will see 9.1 then 9.1.1 then 10.0 then... So?

:laugh:

It sounded more like "we try to do it this year".

8.5.1 is mainly supposed to bring bug fixes, not new features.

This sounds like a very good idea to me... Let's hope this dream really comes true ;)

(I heard, they were talking about a version 8.0.1 after the 8.0 desaster, but it was never released, because NI considered it too expensive. :thumbdown: )

Posted

QUOTE(silmaril @ Oct 19 2007, 09:24 AM)

:laugh:

It sounded more like "we try to do it this year".

8.5.1 is mainly supposed to bring bug fixes, not new features.

This sounds like a very good idea to me... Let's hope this dream really comes true ;)

(I heard, they were talking about a version 8.0.1 after the 8.0 desaster, but it was never released, because NI considered it too expensive. :thumbdown: )

I believe since NI embraced the SSP they try to get a new release around august (NI week) and a patch (x.x.1) in January/February.

LabVIEW 8.0.1 was released as an upgrade but their was a lot of complaints about the Recompile time and NI decided to roll out an installer for 8.2.1 meaning you needed to relicense and not everyone that had 8.2.0 could install 8.2.1

Ton

Posted

QUOTE(jpdrolet @ Oct 19 2007, 07:13 AM)

Not quite... Remember?

I do now. School bus yellow and the VI medallion that looked like the new 3D controls. Maybe someone could add the LabVIEW splash screens to the wiki (with Easter egg variations).

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.