Showing results for 
Search instead for 
Did you mean: 

Bug in the table selection size

Go to solution
An annoying bug in Table controls (LV 8.5/Windows XP/ MacOS 10.5)

When dealing with whole rows/colums (click in the row/column header), the Table Selection Size is always wrong :
when columns are selected, the overall table size is returned,
when rows are selected, the right row number is returned, but the column number is set to 1 !..

The attached vi shows the problem.
Chilly Charly    (aka CC)
Message 1 of 7

chilly charly wrote:
when rows are selected, the right row number is returned, but the column number is set to 1 !..
Confirmed in LV 8.5, Win XP!
You mean to say that the right row number is returned in the Selection Start property, NOT in the Selection Size property, am I right... ?
Because, the Selection Size always shows 0, when the row header is selected...
- Partha ( CLD until Oct 2024 🙂 )
0 Kudos
Message 2 of 7
Accepted by topic author chilly_charly
Since this bug was a showstopper for my application, I spent some time trying to find a workaround...
Found one by accident. I don't understand why it works : it should not do anything :
Detect a mouseUp event in the row/column headers, then read the Selection start position and write it back in the... Selection start position (ie : do nothing) ! That's enough to get the right value out of the Selection size...
The attached vi illustrate the above story.
Chilly Charly    (aka CC)
Message 3 of 7

Hello CC, I didn't see a follow-up from any NI employees on this thread; did you report this bug to NI through phone or email?  If so, could you please post the bug ID to this thread?  If not, please let me know and I'll try my best to find someone to look into this.



Travis M
National Instruments
0 Kudos
Message 4 of 7
Hi Travis,
I didn't report the bug elsewhere. Thanks for your attention.
Chilly Charly    (aka CC)
0 Kudos
Message 5 of 7

Message Edité par chilly charly le 03-16-2008 06:35 PM
Chilly Charly    (aka CC)
0 Kudos
Message 6 of 7

The bug is still there in LV 2015.

The workaround works well.


Message 7 of 7