Monthly Bugs, August 2007

[Ray.R]

See this thread..

[Jim_Kring]

---

@duffman Says: wrote:
Hello Jim Kring,

I want to be sure that we properly address the bug that you reported entitled "Get LV Class Default Value.vi" can't open lvclass within LLB in built EXE" which was reported in a non-NI forum to which you linked. If you would, please start a new thread in the NI Discussion Forums with all of the information about the bug. Please post back to this Monthly Bug Report Thread with the link to the new thread. Thank you very much for your time.

Mike D.

---

Mike,

I don't understand why you want this.  I posted a CAR number -- that's how NI tracks bugs.  Please explain more about how posting to the NI forums will help you "properly address the bug".

Thanks,

-Jim

[aartjan]

I posted some 8.5 project and builder issues in this thread:
http://forums.ni.com/ni/board/message?board.id=170&message.id=271565

Aart-Jan

Message Edited by aartjan on 09-14-2007 01:53 PM

[altenbach]

The linked thread show a situation where the "formula waveform.vi" incorrectly flags valid formulas as invalid.

LabVIEW 8.5 only. Works fine in 8.2.1!

http://forums.ni.com/ni/board/message?board.id=170&message.id=271812

[Ray.R]

Error 66 remote access in LV8.2.1 reported by Mike Porter

[altenbach]

The following VI was posted

http://forums.ni.com/attachments/ni/170/271684/2/Testing%20Blocks2aexp.vi

Opening it, will cover everything on my screen (1400x1050) and I cannot even reach the start menu, task bar, menus, or title bar.

Details: http://forums.ni.com/ni/board/message?board.id=170&message.id=271880#M271880

Shouldn't LabVIEW put some boundaries on the window size so this cannot happen?

[Travis_M.]

I just wanted to take a second to comment on your question:

“I don't understand why you want this.  I posted a CAR number -- that's how NI tracks bugs.  Please explain more about how posting to the NI forums will help you "properly address the bug".

Since you already have a CAR filed for your issue, I think that posting it again to the NI boards won’t really help us address the bug itself, but rather it might help us in the future if we want to send out updates to people on the issue.  For example, when we released 8.2.1 Travis H went through and posted many updates to threads when bugs were fixed.  We used the special “this was reported to R&D” keywords for our search of the NI discussion forums (for example: http://forums.ni.com/ni/board/message?board.id=170&message.id=207833#M207833).

Another advantage to posting a link to a NI board in the bug forum (oh, and another reason to make sure a new thread gets started each month), is that on the second Tuesday of each new month I have a reminder set up to review each posting from the bug forum.  If the bugs are reported to an NI board it’s easy for me to track down which AEs may have been working on the issue to follow up with them on anything else that may need to be done.

I hope this helps clear things up-

[Jim_Kring]

Hi Travis,

Thank you for taking the time to explain how NI works hard to fix bugs and communicate that to interested parties.  We appreciate your efforts.

By the way, Laura F. has volunteered to update the wiki page on LAVA called "LabVIEW_Bug_Reporting" (that describes the suggested bug reporting process for LAVA members) to include more information about how to use the "Report a Bug" feature of http://ni.com/ask.  Would you be interested in working/communicating with Laura to make sure that the wiki page also describes how NI uses the discussion forums on ni.com to track and follow up on LabVIEW bugs?  This will help LAVA members (and other LabVIEW users) to better understand the process and how to most effectively report bugs to NI.

Thanks,

-Jim

[Ben]

See this thread

Ben

[Ben]

See this thread

Ben