Great list! I was waiting a long time for it. Now I have a place to look for strange effects I cannot explain. (is it me or labview?)
Problems such as http://forums.ni.com/ni/board/message?board.id=170
Is it possible to make the 'reporting of issues' more clear?
The primary reason we don't post all publicly reported bugs is mostly trying to reduce noise. If we think including a bug is more harm (in the way of noise) than help, we leave it off. There are numerous considerations that go into arriving at that conclusion. If the odds of someone encountering the problem are rare or extreme (e.g. enter a name for a VI that is more than 32,000 characters long will crash LabVIEW), we might not include it. If there is no value in forewarning a user of an issue, we will not include it (e.g. a dialog box field label is misspelled, but still recognizable).
...Could you ensure that all publicly posted bugs be included in the LKID ?
Hello everyone, we have updated the format of the Known Issues document for LabVIEW to include a couple more fields and we've split the two tables into two separate documents to make it a bit easier to find the information you are looking for. I hope you like it!
Edit: I also added a document which describes what each category means. You'll notice that Upgrade Issues is now split into two types of upgrade issues. Read about it here.
Travis, I am missing at least one issue:
Can't change decimal sign in timestamp
See here http://forums.ni.com/ni/board/message?board.id=170
Hello Ton, Thanks for bringing this issue to our attention. Unfortunately, we can't document every issue that is reported; but we do try to focus on the most commonly or more severe problems. I found this CAR in our database, and I'd like to discuss it further and discuss its inclusion in the Known Issues Document. I'll reply to the thread it was reported in sometime today.
The list is a little bit out of date (or incomplete).
Travis mentioned:"The issue should appear the next time the known issues document is updated"
However there is nowhere to see when the list is updated.
And I think that when a car is generated there should be feedback to the contributor, the list is a great tool for that.
You could even set up a page with 'rejected bugs'.
Thanks for the great feedback. The best way to approximate the last update date is to take a look at the known issues by date document and look at the date of the last entry. That is typically the last update date +- 5 days. That being said, you are right -- it has been a while since it's been updated. Part of the reason for that is that I have just recently moved into another role in R&D and am no longer working with LabVIEW-support related duties so the project hand-off has added to the delay (I do know for a fact that they are working hard to get another update of the document soon).
I agree with your suggestion that having a "last update date" is a really good idea for the known issues list. I'll make sure the new person who works with the document gets that suggestion.
Thanks for contributing, and keep the feedback coming!