cursor flicker when closing or flushing a file

[Ben]

---

mvickerman wrote:
Found out what the problem was.  The data file that I was writing to was included in my LabVIEW project.  So I guess it was trying to update the project every time I updated the data file.  Once I removed the data file from the project, everything was fine -- no hourglass flicker on the cursor.  Thanks for all the replies.

---

please mark that post as solution.

Ben

[LabBEAN]

mvickerman,

Could you clarify whether your problem was related to having the data file in your LabVIEW project or in an Auto-populating folder within the project?  That is, if you are using Auto-populating folders, right click the top level folder containing the data file and select "Stop Auto-populating"?  Did this fix the problem?

If so, we know the problem is more specifically with Auto-populating folders and not simply adding a file to the LabVIEW project.  (I saw the behavior specifically with Auto-popluating folders.)

Thanks,
Jason

[Hillman]

Hi All,

Thanks for your hardwork and keeping the community the great place it is for finding support.

I have looked at your code Jason - and it does indeed work well. I also removed the lvproj file and it prevent the hour glass. However, this to me appears to remove the auto-populating mechanism.. which in a around about way is what your advising. The negative to removing the project is losing the hierarchical view of the project...

Anyways, I to mvickerman would be interested in your response.

Also, for the future - users who prefer to use the KnowledgeBase method for seeking answers I will write an article concerning this.

Thanks again all,

[mvickerman]

I had removed the entire directory from my project before checking whether is was auto-populating or not.  My guess is that it was.  As a test, I added the folder back to my project (as a snapshot), and there is no cursor flicker.  So it looks like the problem is just with writing to a file within an auto-populating folder in the project.

[LabBEAN]

Thanks Hillman.

For the record, I still choose to use Auto-populating folders.  I built the demo project to prove to myself that Auto-populating folders caused the issue.  Like most, we build applications (EXEs) for customers, and the data files do not lie within the development hierarchy.  For that matter, the customer doesn't typically have the LabVIEW project open if they have LabVIEW at all

So, deployment resolves the issue.  As the developer, I just wanted mvickerman to know there was a logical explanation for what he was seeing.

Take care,

Jason