tdm VIs in LabVIEW cause editing to go too slow

[PJS]

When modifying LabVIEW code containing a number of TDM file storage VIs, the LabVIEW editor is slowed down due to some process running that keeps updating the TDM VIs.  Is there a simple way to avoid this.  I have thought about encapsulating  these VIs in subs, but this seems ludicrous.  Any other ideas?

[JLS]

Hello,

Can you post a simple example so that I can recreate the behavior with your code?  In the very short term, you could replace those VIs with "dummy VIs" with the same name - just create a VI with the same connector pane and have it open in memory when you load your other VI (the one containing the tdm VI you'd like not to be in memory because of the problem you are seeing).

I look forward to hearing back from you!

Best Regards,

JLS

[PJS]

attached is the VI in question.  It is intended only to be used for editing as that is the purpose of the post.  It is not meant to be executed and I will not post the corresponding support files. 
Thanks for the help.

[JLS]

Hello,

I indeed see the behavior you describe with your VI, and am able to recreate the behavior with one of my own.  It seems that the editing latency we are experience is proportional to the number of TDM VIs on the block diagram.  I have filed an official corrective action request to R&D, which included a description of the problem, a link to this forum, your llb, and the VI I created in order to demonstrate recreation of the problem.

I apologize that you are seeing this behavior, and hope that I can indicate a solution in this stream soon!

I will post with whatever I can as soon as possible!

Best Regards,

JLS

[PJS]

please contact me by private email.

[JLS]

Hello,

Sure, I can respond to you by private email, however, can you post your private email address?

Best Regards,

JLS

[JLS]

Hello again,

Ok, I have confirmed that there is only a workaround at this time, and it is indeed to wrap them into subVIs.  Perhaps you can wrap some code including some of the TDM VIs into subVIs.  The fewer you have in your top level, the better of course in terms of editing latency.  Unfortunately, I was not given a date for a fix, but what I can tell you is that it is now a known issue.

I hope that the subVI workaround is acceptable in the mean time.

Best Regards,

JLS

[PJS]

I have issues with responding to posts from work, so sorry for the delay.   So here is the message that I wanted to post earlier...
I thought that you worked for NI?  If so, please contact me at schlagheck+p+@us+.panasonic +com (remove the plus signs).  If not, then I am sorry that I can not carry on the thought process for which I suggested the private email.

I have already encapsulated the VIs in question.  Now the big issue is getting the time stamp data type to work as  a custom property.

Thanks,
Paul