close slowly for front panel

[Dennis_Knutson]

Define slow. Are you talking milliseconds, seconds, minutes?

[billko]

---

@labmaster wrote:

crossrulz,

so, is it natural to shut down slowly or is there any other way to shut down?

---

Just don't be in a rush!  Let it close down naturally.  Sometimes it takes time for services to close, buffers to flush and stuff like that.  It also depends on how effeciently you've coded your VIs.

For example, one of my tests takes about a second to close because of all the data files the sub-tests write.  So the main loop waits around until the writing loop signals that it is done writing the data.  (In this case, the sub-tests finish way ahead of the the file writes.  In others, the write loop can catch up while the longer sub-tests are running.)

[labmaster]

Unfortunately, as I knew, the speed of closing FP is  not related to  the calling open reference or other.

Is the slow speed the property of realtime in LabVIEW?

[labmaster]

Dennis_Knutson, that's good point. Sometimes, we forgot the unit of quantity.

about 1 sec or more and there were two "same" icons in stopping the application in taskbar.

I have no much experience about the run-time application so I am curious if this is right.

That's what I asked.

[labmaster]

billko, I meant two point: slow and two icons in taskbar in stopping the (runtime) application.

[billko]

As Dennis asked:

How long is it taking to close down?  And do you have more than one data point to work with?  (i.e., Do you have other LabVIEW VIs that close more quickly?)

And why is speed so important to you that you are willing to crash the application to get it to close more quickly?

[labmaster]

billko, maybe you didn't understand what I mean.

When I stopped my application built by LabVIEW, I observed one more same icon was appeared in the taskbar.

So, the killing time is around 1 sec. This is enough time to feel a person it is delayed. That's the reason why it is important.

My question is regarding proper phenomenon in runtime mode.

Someone pointed out my mistake in open application reference in closing FP.

But this is not related solution.

[billko]

---

@labmaster wrote:

billko, maybe you didn't understand what I mean.

When I stopped my application built by LabVIEW, I observed one more same icon was appeared in the taskbar.

So, the killing time is around 1 sec. This is enough time to feel a person it is delayed. That's the reason why it is important.

My question is regarding proper phenomenon in runtime mode.

Someone pointed out my mistake in open application reference in closing FP.

But this is not related solution.

---

I think your expectations are unreasonable.  Try running your browser from a batch file, then see how long it takes to close after you exit the application.  It will probably take a few seconds to close the command prompt as it finishes its housekeeping.  Especially if you've been browsing aorund a lot.

[labmaster]

billko, Thanks for the response.

okay, let's forget the delay and I had better admit the feeling could be different person to person.

Just think about the copy of the icon in stopping an application..

I think this is also unusual event (refer the capture in my orginal first posting).

Visually, I can feel some more delay due to two same icons.

[crossrulz]

---

labmaster wrote:

Just think about the copy of the icon in stopping an application..

I think this is also unusual event (refer the capture in my orginal first posting).

Visually, I can feel some more delay due to two same icons.

---

I remember seeing that before.  Unable to reproduce in my latest applications.  Do you have any code that shows this behavior?