XControl facede.vi - Events that are triggered when a new instance is opened.

[Ben]

Van,

Could you post the CAR associated with this investigation?

Ben

[Vsh]

Hi...

thanks for the responses.

Van_L wrote:

Vsh, I am curious how this behavior is affecting your application.

Thank you for your patience

---

Van,

I am doing lot of things in data change event. Which should execute ONLY when data is written to the XControl's terminal, value property, or local variable.

Now, it also triggers when a new instance is opened, I can digest it by avoiding it for the first call. But triggering two times, I have no control over it. (Because the second time execution may be due to the actual data is written or may be because of a control reference which was placed on owning vi's block digram).

Even the documentation says that this event will execute when a value was written to the XControl's terminal, local or value property. But it is not actually so. It also executes when a new instance is opened.

Also it is quite not clear why all the default events should execute when a new instance is opened. I think only one event( display state change or a new one!!!  ) must execute when a new instance is opened. May be I am wrong, there may be a reason for that. Points are most welcome explaining the reason.

Thanks.

Message Edited by Vsh on 03-31-2008 09:45 AM

[Van_L]

Hi Vsh and Ben,

I have submitted a CAR for this with CAR # 100580

I have put detailed description and I also notice that this behavior happens to cluster of array as well.

R&D will take a look at this and hopefully can clear up the confusion

Thank you for you patience and I will continue the investigation as well

[Van_L]

This was reported to R&D (# CAR ID 100580) for further investigation.

We are continuing looking into this issue.
Your patience and feedback are greatly appreciated.

[Ben]

Thanks Van,

I teach my developers and customers to watch for the asterisk as a sign that something has changed. This BUG complicates that statement. For apps that use the XControls we can not rely on the asterisk but rather have to watch the close dialog that says "5 VI's need saved". If it more than normal then I have to remember which ones always need saved to find out which VI is asking to be saved.

Yes this sounds very anal and nit-picky BUT.... You only have detangle one app with 700 sub-VI's being developed by five developers to appreciate the importance of the ASTERISK.

Ben

[Travis_M.]

Ben, I added your comments directly in the bug report.  I understand the difficulty the 'dirty dot' can have on developers for the reasons you cite and other common source code control issues that come with this.  Thanks for posting those comments, these things help our AEs and us understand the full impact an issue may cause someone which helps us prioritize fixing our bugs.

Have a good week-