Tree Select BUG?

[miguelc]

Came across a little problem, don't know if I'm doing something wrong or if it is a genuine bug.

Here's what I'm seeing:

1) I run a program that at the beginning deletes all tags in a tree using the Delete Items Invoke Node with an empty string constant and a True constant for the Delete Children part.

2) I select all the items in the tree, and display all the tags from the tree using the All Tags Property Node, and display the selected tags directly from the output of the tree icon.

3) I rerun the program, which deletes all the tags as mentioned before, use a different data set, select all those items, and when it displays All Tags it only has the tags from that run, BUT the Selected Tags has all the selected tags from the current run AND all the tags from the previous run.

The solution of course is to simply create a local variable of the tree and at startupwire an empty string arrary to it. This shouldn't be necessary if the Delete Items deletes all the tags.

Attached is a VI showing the BUG

Michael

Additional NOTE: If you continue running the VI, the selected tags will pile up UNTIL you manually right click on the tree and hit "Delete All Items"

Message Edited by miguelc on 03-02-2007 10:46 AM

[JLS]

Hello,

Before I dig much deeper - you have some code in parallel that's sitting to the left of your sequence structure.  There are 2 pieces which are not connected to the structure by dataflow - this means those pieces may or may NOT execute before the sequence structure executes.

Make sure to use dataflow to dictate the sequence of operations precisely (or use sequence structures, but you should use dataflow whenever possible - error clusters are a convenience way to do this), and then re-evaluate your code.  If you still think there's a problem at that time, repost and I'll take a closer look!

Best Regards,

JLS

[miguelc]

Good point. I just stuck them in the flat sequence. Same bug is happening.

Michael

[JLS]

Hello,

What version of LabVIEW are you using? 

I tested on 8.2 and I do not observe the behavior described on the front panel of your VI.  The Selected Tags list only shows oranges after the second run - it does not keep the apple tags.

This could be an old bug which has been fixed if you're not using 8.2.

Best Regards,

JLS

[miguelc]

Aha! I think I narrowed the bug down. I am using Labview 8.2. The reason you may not be seeing what I am seeing is because I hold down <ctrl> every time I select items in the tree. I found if you select all of the items with Shift, it works properly. BUT, if you hold the ctrl button, it will include selected items from the previous run.

Try this: 1) Run the VI with the Apples data set. Select only the first Apple in the tree WITHOUT holding any buttons.

              2) When the VI stops, change the data set to Oranges, and run the VI. While holding down <ctrl>, select the first Orange.

When I run it this way I see Apple then Orange in the Selected Tags. Only Orange should be there if the tree selected buffer was flushed between runs. Maybe NI wants it this way? I think its improper function.

Michael

[JLS]

Yep, I see exactly what you mean now, and it's a bug. 

I actually found a CAR noting this issue upon a finer search: CAR ID: 45TDTLV6

Sorry the any inconvenience - it's being addressed for a future version of LabVIEW.

Best Regards,

JLS

Standard CAR response:

" This was reported to R&D (45TDTLV6 CAR ID) for further investigation. Thanks for the feedback! "

[miguelc]

Thanks JLS.

I'm kind of a newbee. What is a CAR? Can anyone search these CARs before posting a supposed bug like I just did? Can you find them online, if so where?

Michael

[JLS]

No problem 🙂

>>What is a CAR?

CAR stands for Corrective Action Request - it's a formal bug report to R&D.

>>Can anyone search these CARs before posting a supposed bug like I just did? Can you find them online, if so where?

We post the CAR IDs online so that customers can follow up with them if they'd like, and easily refer to them.  The LabVIEW Champions maintain a monthly bug thread where you'll find pretty much everything BUG that's been posted online - if you search the forum for "monthly bug" (quotes not necessary) you'll see a slew of monthly bug threads returned.  You can also search the forum in general for keywords related to your bug, to see if anyone else has reported it.  Of course there is also a bug list/database which is maintained internally at NI, but the public doesn't have access to that.

I hope this helps!

Best Regards,

JLS

Message Edited by JLS on 03-08-2007 11:35 AM

[TheGreenStump]

Hi kids...

It's been a while since this post saw any activity. Have there been any developments on this bug? I'm using Labview 9.0f3 and I'm experiencing the same thing. I programmatically delete all the tree items just as explained in the help file, but the items from the next run are appended to those from the previous run, just as the original post described.

Strangely, if I change about anything on the block diagram and then change it back before running again (e.g. create a broken wire, then fix it right away), even if I change something which isn't related to the programmatic deletion of the tree, the tree functions as it should. But if I run again without messing with the block diagram, the appending happens again. Weird.

Please just give me a heads up as to whether this has a resolution yet.

Thanks,

TGS 

[Eli_S]

Hi TGS,

I looked up the information for the CAR referenced earlier in the thread, and that issue was deemed to be expected behavior. The reasoning was that in order for the tree control not to save the tags, the actual control terminal has to be updated. Manipulating it through property nodes alone, will not clear the tags.

Please let me know if you have any additional questions.