Application, once built, shows "Not Responding" in the toolbar, and it doesn't go away

[alecjcook]

If you have an application that is running with some kind of timeout, (My application will send a message, and wait for a user definable period of time for a reply). If this tine is over 5 seconds, and the user clicks on the application, the app sets its status to "(Not Responding)". This is mirrored on the toolbar.

Once the application begins responding again, the title bar of the app changes back to an active state, although the representation of the app on the tool bar stays in a "(Not Responding)" state.

    I have attempted to stop the user click having an effect by setting the cursor to busy and setting the "Click Disable" to TRUE, but this does not help.

Any ideas how to get round this one? Or is it a bug?

Cheers, Alec

[muks]

Are you using any pluggins?Are you low on memory?Can you post your code?

[Owen.S]

Hi Alec,

Just a few questions about your problem. Is the "Not Responding" status intentional?, if so then you could use some other functions to stop the user interacting with the VI while it is running. Also what version of LabVIEW are you using? and do you have any screenshots or example code?

Cheers, Owen.

[alecjcook]

Note, this application has been built as a .exe file.

Also, i am using LabVIEW 2009

[Owen.S]

Hi Alec,

I think this might be a windows related issue rather than LabVIEW but there are number of ways around it:

http://forums.ni.com/ni/board/message?board.id=170&thread.id=359838&view=by_date_ascending&page=3

This post might be of some intrest. You could display a "Loading bar" or similar screen while the program sends and recieves messages to hopefully stop this problem. There is also an example in the help files which I have attached with this post.

Let me know if you need anymore help.

Owen.S

[muks]

Do you have the administrative rights?

[alecjcook]

I must not be explaing myself propperly.

Every application that is open has an instance in the task bar

As you can see here, I am running outlook, labview, firefox and MSN, but don't tell my boss 😉

Somtimes, when windows things an application has crashed it will place the phrase "(Not Responding)" next to it's name in the task bar. It will also place the word "(Not Responding)" In the title bar for the application.

I have written a program that calls a .dll. The function of this .dll is to read incomming data up the RS-232 socket of my PC. I can set a timeout on this, lets say I set it to 1 minute.

The application is running, I call the .dll to read incoming data, then I don't produce any incoming data. The application will wait, up to 60 seconds for some data, but in the mean time, Windows thinks the LabVIEW executable file has crashed, so places the word "(Not responding)" in the taskbar AND in the title bar. At this point I send my data up the 232, the data is received and displayed by the application. At this point Windows forgives LabVIEW and the "(Not Responding)" status is revolked. This phrase is then removed from the title bar, but IS NOT removed from the task bar.

Does anyone know if we have control over this, or should I report it as a bug to National Instruments?

Many thanks guys,

Cheers, Alec

[rsw]

Hi Alec,

That sounds like a very unusual exception to have occuring, the actual "Not Responding" is handled by the Windows task manager to ensure a process co-operates within a set time period (you've probably seen it before on other applications that fail to load quickly). The fact that Windows then realises the process has returned to a state it deems as fine and clears the "Not Responding" tag on the title bar is also normal, however this should also clear on the task manager as this is just a reference to the title bar.

It appears that you are running a theme program of some sort ontop of Windows XP? I would recommend turning this off (if you can) and seeing if it still appears to rule that out. I'm not sure in this case if its an issue with LabVIEW or a Windows reporting error therefore, if possible could you attach the code or a cut down version of the code and I will try it on my system to progress finding the cause of the fault.

All the best,

Rob W