The bug in "\examples\comm\dotnet\GetWeather.vi"?

[Rashid]

Hello!

Preamble

I was looking the answer on the following question:

Can I generate my user event in the main VI so that subVI in subpanel got it and stopped its while loop with event structure inside

(infinite timeout is attached to event structure)?

Bug detected

When studying the shipped sample GetWeather.vi where user event is used I got that it's not working as it should (or more exactly,

as I think it should). Am I right?

See attached for the explanation.

Best regards,

Rashid.

P.S. If someone knows the answer on the question above, I'd be appreciating your help. Thanks in advance.

(It seems to me that the answer is NO, I mean there's no way to do that with events and I have to use global queue or global var

and attach timeout to my event structure to poll the global in my while loop sometimes).

[Rashid]

As to my question about using user events across VIs, I think I found an answer

http://forums.ni.com/ni/board/message?board.id=170&message.id=154615&view=by_date_ascending&page=1

Thanks to Evan.

Regards,

Rashid.

[Ankita]

Hi Rashid,

I have reported the bug in Get Weather.vi to R&D (# 3UQG47G8) for further investigation. Thanks for the feedback !

Regards,

Ankita

[Rashid]

Ankita,

Is there somewhere R&D bugs (bug tracker) published in NI site, or it's for internal use only and your message details (I mean bug ID) is for NI developers?

I failed to find it by search.

I'm interested in this as I see the bug IDs in posts on the forum not first time and thought maybe my bug posts aren't in appropriate place.

Regards,
Rashid.

[Ankita]

Hi Rashid,

You have raised a very valid point. Well here is the story behind it.

Until a few days ago, when ever customers reported bugs via Discussion Forums, we used to verify and reproduce the reported behavior and then file a Corrective Action Request (CAR) to R&D for further investigation. These CARs (with an associated ID) are internal-only documents that we use to keep track of the investigation progress. However some customers wanted to know the CAR ID so they could call/email NI technical support and ask for the status of CAR ID so and so. Moreover some of our developers (who frequently answer Discussion Forum threads) wanted to see the CAR ID on the forum so as to ensure that the bug actually got reported to R&D thus avoiding any repetitive work.

Hence we have started to post the IDS of the CARs that we have created for the reported "bugs". I hope this makes things clear.

Regards,

Ankita

[Rashid]

Thanks, Ankita!

Now the things are clear.

Regards,
Rashid.