Table flicker and color bug?

[tst]

The table tends to flicker when being clicked on for a selection.

A very old thread (2001) suggests placing a control over the table to cause invalidation, which works, but seems a bit weird when you consider it's already 2005.

Also, using the BGColor property on a selected cell only updated the cell after it has been "unselected", which requires 2 additional clicks on the table.

I don't use tables usually, but I would still consider these bugs (and annoying ones).

[Chaos]

Sorry about this very odd looking code but it does seem to fix the problem updating the BG color of the selected cell.

Although for the life of me I could not tell you why.

Note: The order of executing the nodes is important.  Reversing or removing the depandancy between them can affect if or not it colors right...

[Philip_Courtois]

Hi tst,

Your observation sounds similar to the one reported in the following KB:

Background Color of Table Updates Slowly in LabVIEW

At least the LabVIEW developers are aware of the issue, and are working on fixing this for future releases of LabVIEW.

Thanks for reporting though!

[tst]

Sorry, Philip, but there are 2 problems I refered to, and the text in that article doesn't seem to relate to either of them.

I did not see problems with the update speed, but with the flickering and with the "delayed reaction".

Download my VI to see exactly what I mean.

[EVS]

Dear tst.

I have changed Table mode from indicator to control. You can just modify any cell, table will be flick. It is not neccessary to Run VI

It seems to me this bug is corresponding with the Table Control. When yoiu press mousebutton the table try to initiate edit mode to change cell text even if indicator mode. So the first mouse up does not recognize as mouse up, it ends edit mode.

Sorry for my English, I hope it is possible to undestand me 🙂

Evgeny

Message Edited by EVS on 08-26-2005 03:10 PM

[Philip_Courtois]

Hi tst,

I'm sorry for being too fast in deferring your two issues... You are indeed right that the issue from my link doesn't cover the issues you are mentioning. I have made sure that the LabVIEW developers are aware of the two issues so they can improve future versions of LabVIEW.

Thanks for posting this feedback!