Monthly Bugs, January 2009

[RavensFan]

With LabVIEW 8.6 a method was made public to allow an object to be highlighted.  This works in runtime mode, however the documentation states it only works in edit mode.

CAR# 142918

[Mathan]

Open/Close All Items have disappeared from the shortcut runtime menu of a tree control when the application is built

CAR: 142872

[Mathan]

When using stacked plots with wfm chart and in the event case structure 'Shortcut menu activation' I cannot independently change the autoscale settings of the Y axis.

(Details)

[Mathan]

In LV 8.6, when a VI is embedded into a subpanel on another VI, when you right-click on the panel of the embedded VI and select "Open Block Diagram", nothing happens.

Corrective Action Request (CAR) number is 124113

[Intaris]

Performing a "find and replace" on a block diagram and choosing a boolean constant from the Boolean Palette set by default to "True" results in an error "Merge VIs not found" whereas choosing a Boolean constant set by default to "False" works fine (For both true and false constants.

 

Confirmed bug, known to NI since last June but they won't give me a CAR... 

Shane.

Message Edited by Intaris on 01-29-2009 11:25 PM

[tst]

Shane, you should probably start another thread for this.

Incidentally, this is probably the same for any merge VI, not just for the true constant. As a side point, I assume that NI created it as a merge VI because it was easier than writing the code necessary to drop a boolean which doesn't have its default value.

[Intaris]

Tst,

why a seperate thread?  I've already been in touch with NI on this, and it's definitely a Bug.

Can I stay if I get a CAR#? 

Shane.

[tst]

---

Intaris wrote:

why a seperate thread?

---

For the same reason you don't put all your data in a single database table - order. That's why we came up with the rules which probably appear in the first post of this thread.

[Intaris]

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

1. One post/bug!
2. One bug/post!
3. No discussion of bugs. All discussions of a bug must take place in the original linked thread.

---

Understood.

At which point our discussing the bug is actually against the rules..... 

Shane.

[Mathan]

February has arrived, so this thread is now closed. Let's continue in the brand new February 2009 bugs thread.

Message Edited by mathan on 02-03-2009 10:40 PM