Monthly Bugs (October 2005)

[altenbach]

This is the continuation of the September 2005 monthly bug thread.

Rules:

Each post here should only contain a brief description of a bug, together with a link to the thread where it is being discussed.

One post/bug!

One bug/post!

No discussion of bugs. All discussions of a bug must take place in the original linked thread.

With LabVIEW 8.0 coming out, this could be a very interesting month! 😮

Message Edited by altenbach on 10-04-2005 10:00 AM

[Ben]

This link points to another example of the graph scaling bug that CC was working on last year. Since his work took place before the bug threads were started, this issue was not previously reported in our bug threads.

Summary:

Autoscaling of the graphs and charts will do some very bad things if the amount of space required to add the marker values for the Y-axis over-laps the graph region. Under the WRONG conditions, the viewable area will walk completly of the screen.

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

Ben

[Ben]

LV 7.1

This thread

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

discusses a bug that causes LV to crash if a re-entrant VI that is set for sub-routine priority is called dynamically.

Setting the VI for "normal" priority is a work-around for this issue.

Ben

[chilly_charly]

Are ActiveX controls compatable with tab controls ?

This is not to the case when using a Microsoft Forms 2.0 TextBox ! The problem is interesting since the control disappears, but is still functionnal : you can write and read it, but you can't see it !

The problem was found by Daniel Blanzat here

[AutoMeasure]

Hi, folks.  I haven't used these NI-hosted forums before, and I'm happy to be trying them out.

Ever since Labview's Unbundle and Bundle By Name functions became able to automatically correct themselves after a cluster element label change (LV5 or 6?), there has been a problem of destructively self-altering code while editing.  The problem became worse with LV7.  Happily, LV8 appears to have fixed most of the trouble.  But I was able to construct 2 examples in which LV8 still exhibits the problem, and I've posted the VIs into the following LAVA threads:

http://forums.lavausergroup.org/index.php?showtopic=2146
http://forums.lavausergroup.org/index.php?showtopic=2157

Please consider this a report of a pain-in-the-neck LV8 editing bug, in which your code can change without you noticing.  Thanks.

[Charlie S.]

I have filed a CAR on this issue -- thanks folks!

(Thanks too, Ben, for bringing it to our attention!)

[altenbach]

In LabVIEW 7.1, it seems to be impossible to write a lvm file using comma seperators. The selection does not "stick".

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

(Seems fixed in LabVEW 8.0)

[Ben]

In this thread you can find an example that shows that a "property node >>> Value" node does not update when the order of the cluster is changed.

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

This is just an FYI because I already reported this bug a long time ago. I really hope this has been fixed in LV 8.

Ben

[Roy_F]

Continued at: Monthly Bugs (November 2005)