Frozen Windows

[MogaRaghu]

A normal data logging software using a few express VIs and daqmx functions to plot 2 different analog channels behaves very funny suddenly for no obvious reason.

The program itself runs without problems and responds to all user commands. But the rest of the desktop includng the system tray and task bar icons simply freeze as long as the VI is running. I tried checking the CPU usage by minimizing the performance analyser in the system tray. Even that froze. The START button in the task bar also does not respond. The moment I stop the VI all of them spring to life.

Can anyone throw some light on whats happening ? I am using PCMCIA 6024 card + WIn XP Pro + LV7.1

Thanks

Raghunathan

[ElSmitho]

Salutations,

I've got something for you to check..

File --> VI Properties --> Window Appearance --> Customize -->

check in that area, if it's modal, that might be something to look at. I believe, it being modal, prevents you from clicking a lot of other things. At least switching between labview programs... In there, i also believe is a way to prevent people from touching anything else while the VI is running. It might require a bit of research on your part, but that should give you a starting location. The help file should finish off a lot of the small details.

If this is an executable, I think there is a way in there to prevent people from going off the screen until they stop the program. Hopefully, the other ideas along with the help menu will spawn onto what exactly you're looking at.

Sincerely,
ElSmitho

[MogaRaghu]

The first thing that I checked was this Modal stuff. No it is not due to that.

Any way the problem got resolved yesterday.

Unfortunatley both the manifestation and resolving were "on its own" without any contribution from me.

The manifestation ( freezing of other applications ) occured, after I did some cosmetic changes to the code like change of plot colours, label change of a few numeric indicators and the like.

The problem got resolved on its own after I carried out some more such changes. Maybe in both cases there is some coincidence.

(All the code is inside a Timed loop running with a dynamic interval setting fed to the node on the right side border of the loop. It is calculated from an expression 1000/Samples where Samples can only lie between 1 to 50 )

I hope the problem does not surface again when I least expect it.

Raghunathan

Message Edited by Raghunathan on 04-29-2005 08:44 PM