Monthly Bugs (March 2006)

[crelf]

So even if I've found a bug that I know is a bug, I need to create a discussion somewhere first and then link to it from here?  OK- I'll do that in future,

[Ben]

IN this thread

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

you will find a discusion of the nature of the Bug Thread when it was initially developed.

Please try to keep discusions of the Bug Thread in that thread.

The LabVIEW Champions will be discussing the nature of the Bug List in next Thursdays (16 mar 2006) LV Champion meeting.

Please add your comments, request, ideas, and feedback to that thread so that your voices will be heard.

Ben

[altenbach]

LabVIEW 8 only (works fine in 7.1):

Trying to edit text labels (e.g. of a slide with text labels enabled) via the properties page clears the first label.

http://forums.ni.com/ni/board/message?board.id=170&message.id=173514#M173514

Message Edited by altenbach on 03-14-2006 09:06 AM

[tst]

LV detects phantom elements and dimensions when using the Array Size primitve with empty arrays. This looks serious, although luckily, I don't really use multi-dimension arrays.

[Ben]

Setting color of a hidden page in a tab control will crash LV 7.1

http://forums.ni.com/ni/board/message?board.id=170&message.id=174745#M174745

Ben

[crelf]

Replace Array Subset bug, Unexpected behavior - from Dan on LAVA:

...a VI that should generate a 2D array of booleans with a pattern defined inside a case structure and double For loops. I initialize an array of FALSE booleans 8 elements long and then use the Replace Array Subset function to flip some elements TRUE. The first time I run the VI I see a strange pattern effecting one of my cases. In that case, when I try to flip a single element TRUE, the elements before it turn TRUE as well. The second time I run the VI, all elements turn true regarless of what is wired to the Index input of the Replace function!

http://forums.lavag.org/index.php?showtopic=2881

[HDRM]

Hi,

I have found out another issue that could have something to do with this bug reported by me in January 2006:

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

(Bug when using VControls, Slides, Tank etc.)

The same behaviour occurs by using any type of graph in a while loop. After approximately 18000~26000 Loop iterations, the VIs freeze. This happens even with the most simple type of graph, the waveform chart.

Best regards,

Manuel

[crelf]

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

The LabVIEW 8 application builder creates the wrong path in the application's .ini file - my NI-DAQmx.ApplicationStorageFile was set to "applicationfolder\nidaqmx.ini", where it should have been just ".\nidaqmx.ini" - this means that built applications can't find their nidaqmx.ini file and therefore DAQmx calls that use virtual channels and/or tasks bomb out with error -200428 "Value passed to the Task/Channels In control is invalid. The value must refer to a valid task or valid virtual channels."

[Ray.R]

Front Panel tears appart in this thread.. 

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

Not yet proven that it's a bug.  

[chilly_charly]

In snap-to-point mode, the cursor does't snap to the tip of narrow peaks. The problem is specific to waveform graphs. No problem on XY graphs. (LV 7.1)