odd table reference problem with LV8

[jdebuhr]

AT least I think it is a problem..

I have a Table on my main VI, I use a reference to pass it through to a dynamically called vi, then a sub vi within the dynamic one. all the data reports back to the main table correctly, but I use the Edit position property to auto scroll it once the current running test listed on the table is below the viewable space. the table has 14 rows so if row 15 is running it should shift up and does not. the weird thing is that it works fine in LV 7.1.1 is there a new Property for what I want that I am just not seeing?

Jeff

[Mark H]

Hi Jeff,

I don't have an answer for the different behaviour of LV 7.1.1 and 8.0 - but I can suggest a better method to scroll/position the table's contents...

You can scroll the table contents around by setting the "Index Values" (top left cell coordinates) property to an appropriate value (Note:the index control itself does not need to be visible).

Example: If your table always has 14 visible rows then you would need to set "Index Values" to [row=1,column=0] for the 15th row to be the last visible row.

A better bit of programming would read the number of visible rows first, using the "Number of Rows" property, then calculate the required "Index Value" row number = Last Visible Row number* - "Number of [visible] Rows" +1, (and then you may need to take the Max(Calculated Value,0)) - thereby allowing for the number of visible rows in your table to be changed without breaking the code.

*Note: remember the columns and rows are numbered from 0....N.

This should work perfectly irrespective of LV versions - gotta be worth top stars I reckon?

Mark.

[jdebuhr]

Mark,

Thanks.. I also did find it yesterday before I left work, I have yet to implement it. I do however have the logic as you stated to see exactly what row I am in and how many rows there are.

Since I am upgrading to LV8 I decide to clean up code and upgrade/improve areas, this happens to be one of the areas.. Thanks again

[Yunhua]

Jeff D has said " the weird thing is that it works fine in LV 7.1.1 " , and it does not work after he upgrade to LV8.0 ,

But you NI guys suggested him to update the code, why? do you think it is very easy to update the validated code before?that's the solution you NI guys provide?