LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VI (Not Responding) in the taskbar only?

Not sure whether this is a Windows XP thing or a LabVIEW one, so I am posting the question (I have seen that in the past, never bothered to mention it here):

 

I have a Main VI that has a path control with which I try to access a file. The file is on a partition mounted over the network.

When the partition is unavailable, the VI is not responding while Windows is trying to establish the link. Eventually a dialog windows pops up telling me the folder is unavailable.

Cancelling returns life to the VI but its taskbar tab still reads "Name of the VI (Not Responding)". I have to stop the VI for this name to be changed to something else.

Bug? Windows feature?

 

0 Kudos
Message 1 of 10
(3,618 Views)

X

 

you know that is not enough!  do the right thing!

  • example
  • steps to reproduce
  • LV version/ OS / Bitness  dah de wha.........

You are exiitced--- (Again)  Why do you  make us work so hard to duplicate what you do by "Accident?' 

[  (I'm Done with  X Unless..........)


"Should be" isn't "Is" -Jay
0 Kudos
Message 2 of 10
(3,609 Views)

What is there to reproduce that I can show?

You have to try to access an unaccessible drive from a path control in a running VI. Windows for  a while looks for the drive and stalls the VI (VI not responding as shown on the VI Panel Title as well as on the Windows XP taskbar).

Then pops up a dialog window telling you the drive is already in use (or whatever nonsense Windows says in those circumstances). Cancel and return to the VI.

Its window title will be back to normal, but the taskbar tab will still have the (Not Responding) addition.

 

Windows XP 32 bits/ LabVIEW 2013 f2

Nothing to get excited about.

 

 

Message 3 of 10
(3,590 Views)

@JÞB wrote:

X

 

you know that is not enough!  do the right thing!

  • example
  • steps to reproduce
  • LV version/ OS / Bitness  dah de wha.........

You are exiitced--- (Again)  Why do you  make us work so hard to duplicate what you do by "Accident?' 

[  (I'm Done with  X Unless..........)


X-

 

Was that intended?...

 

 

If you want to play...............

 

If you want to learn a thing or two.............(Do not hack me while I am Posting)

 


"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 10
(3,579 Views)

@JÞB wrote:

@JÞB wrote:

X

 

you know that is not enough!  do the right thing!

  • example
  • steps to reproduce
  • LV version/ OS / Bitness  dah de wha.........

You are exiitced--- (Again)  Why do you  make us work so hard to duplicate what you do by "Accident?' 

[  (I'm Done with  X Unless..........)


X-

 

Was that intended?...

 

 

If you want to play...............

 

If you want to learn a thing or two.............(Do not hack me while I am Posting)

 


Damn --- Babys got mr!


"Should be" isn't "Is" -Jay
0 Kudos
Message 5 of 10
(3,577 Views)

Hi X,

 

Thank you for your question. Is there any more information you can give me about your application? What are you attempting to implement? What is the structure of your project and how was it built? Are you getting a specific error code along with the message? 

 

We may be able to establish what the issue is with a bit more information.

 

Best of luck!

National Instruments
0 Kudos
Message 6 of 10
(3,521 Views)

I am not sure how to put it more simply:

take the VI I created for our friend Jeff. Put it in a project if you wish, but that is not necessary. Run it (it does nothing and you need to abort it to stop it). While it is running notice that its window title is as follows:

 

ScreenHunter_001.jpg

 

OK. Now that everything is working, try to open a file (using the little Browser button on the Path control) which is inacessible because it is on a mounted drive...which you have disconnected.

You are going to try that, but you are going to fail, so while Windows is scratching its head, go back to the Jeff Bohrer VI and click on it. Since it is irresponsive, the window title will change to this:

 

ScreenHunter_002.jpg

 

OK. Now, look at the taskbar (it's gone in Windows 8, from what I was told, but I suppose it should be still be around after XP). The VI's tab should be reading something like "For Jeff Bohrer.vi (Not..." the exact number of visible characters depending on your display settings. That stands for "For Jeff Bohrer.vi (Not Responding)", mirroring the window title above.

Now, eventually, Windows will give up and tell you that the folder is inaccessible, with something like this:

 

ScreenHunter_001.jpg

 

Once you click OK (or cancel depending of what happens), the Jeff Bohrer.vi is happy again and the window title goes back to normal.

However, the taskbar tab is still reading "For Jeff Bohrer.vi (Not..."

The Not Responding has stuck and will only disappear when you abort the VI.

 

My question is: besides the obvious annoyance in a built application, should I credit NI or Microsoft for this oversight?

 

0 Kudos
Message 7 of 10
(3,503 Views)

Hi,

 

I was unable to reproduce your results on a Windows 7 computer. What operating system are you running?

 

Best Regards,

National Instruments
0 Kudos
Message 8 of 10
(3,472 Views)

First post says XP. 32 bits. If it ain't broken...

0 Kudos
Message 9 of 10
(3,456 Views)

In my opinion, it sounds like an operating system problem. The not responding case is not handled by LabVIEW, but by the operating system.

 

Apologies for the confusion!

National Instruments
0 Kudos
Message 10 of 10
(3,436 Views)