Monthly Bugs (October 2006)

[chilly_charly]

This is the continuation of the September Bugs Thread

Rules:

1. Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
2. One post/bug!
3. One bug/post!
4. No discussion of bugs. All discussions of a bug must take place in the original linked thread.

[chilly_charly]

Bug with the Read JPEG File.vi, generating error 1 when the jpeg file path use localized chars on MacOS, pointed out here

[altenbach]

Setting marker values no longer correctly updates the axis range in LabVIEW 8.20. (Seems to work OK in 7.1).

http://forums.ni.com/ni/board/message?board.id=170&message.id=208452&jump=true

[altenbach]

Under very specific conditions (other VI running, etc.), the timed loop ignores dt set inside the loop if it is initially set to zero.

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

[TiTou]

LabVIEW 8.20 image display bug when creating a constant on the diagram.

[sth]

Sound I/O routines do not work for LV 8.20 on OS X (intel).
http://forums.ni.com/ni/board/message?board.id=170&message.id=211383
CAR # 3Y1DG95E

[chilly_charly]

Another problem possibly related to constant folding, reported by kostya here
CAR 42M6QJ1W

[sth]

Cosmetic Bug in LLB Manage (extraneous text field)
http://forums.ni.com/ni/board/message?board.id=170&message.id=211716

[MartinP]

0 Digits Of Precision-bug:

In Pre-8.20 LabVIEW-versions, there are no problems to set
a Double indicator or control Format to Floating Point, 0 Digits Of Precision.
In LabVIEW 8.20 however, I'm only allowed to go down to 1 Digits of Precision.
(Trying to set it to zero, gives error 1077, when using the Property node.)

[Ben]

Hi Martin,

Please review the

"

Rules:

1. Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.
2. One post/bug!
3. One bug/post!
4. No discussion of bugs. All discussions of a bug must take place in the original linked thread.

"

The bug thread serves as an quick index only. In the future please start a new thread for the discusion, confirmation, and work-arounds**.

The bug you mentioned was reported as CAR# 40HEDDJG and the fix is scheduled for a "future release"* of LV.

Ben

*I can not be more specific than that!

** If you think our bug list is hard to search now, imagine what it would be like if we mixed in discussions. Use this thread if you have frther comments suggestions or just want to flame me.

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=501&jump=true

Ben