LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

U64 Formatting BUG

There is a bug in the formatting of U64 numbers for some formats and at least one number, in that a colon ":" is displayed in the formatted number or string.  The bug is in (at least) LabVIEW 2009 and 8.6.1.

 

 U64FormatError.png

Message 1 of 8
(3,648 Views)

This was discussed in the following thread

 

http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=423787#M423787

 

 CAR 123331

 

 

Message Edited by Matthew Kelton on 01-28-2010 09:33 AM
0 Kudos
Message 2 of 8
(3,617 Views)
Or maybe CAR 179239, take your pick.
0 Kudos
Message 3 of 8
(3,612 Views)

Thanks - it can be pretty difficult finding out whether a bug is previously reported or not.  Is there a recommended process to use to check and report bugs?

 

Cheers ~ Greg

 

0 Kudos
Message 4 of 8
(3,585 Views)

Hey Greg,

 

The best way to check up on CARs is to follow the Known Issues List (KIL) and the Bug Fix List.  The KIL isn't all inclusive when it comes to bugs; however, we try to update the KIL about once a month. The Bug Fix List is updated with each release of LabVIEW.  This is meant to be as close to all inclusive as possible.  If a bug is reported by a customer we try to make sure it makes this list.

 

On a side note, the real CAR ID for the issue you mentioned is 50785. Smiley Wink  The others were closed because they were duplicates of the previously reported CAR.

 

 

Regards,

Jon S.
National Instruments
LabVIEW NXG Product Owner
0 Kudos
Message 5 of 8
(3,577 Views)

In the Breakpoint forum, there is a new thread each month for bugs.  But, that can still be difficult to search through.  There is an open issue list for 2009 here.  It may be a little less of a headache to search through, but these will only be issues that NI has recognized and documented (which, to be honest, is most of them).

 

The only reason I linked to the other thread is because I had commented in it and remembered seeing the issue before.  It still took me a few search tries to get the right keywords for it to show up.  Sometimes, you'll just miss it.

0 Kudos
Message 6 of 8
(3,575 Views)

Jon S. wrote: 
 

On a side note, the real CAR ID for the issue you mentioned is 50785. Smiley Wink  The others were closed because they were duplicates of the previously reported CAR.

 

 


 

See, even NI can't find bugs that have already been reported before.
0 Kudos
Message 7 of 8
(3,570 Views)

And CAR 50785 isn't even in the KIL.  Oh well, as long as the system works well for those who have to fix them...

 

0 Kudos
Message 8 of 8
(3,544 Views)