TWebStringGrid dynamic row add: cell value not written to last row

WEB TMS WEB Core
1

Hi Bruno,

I'm trying to dynamically add a new row to a TWebStringGrid and populate a cell in the first column of that new row when a button is clicked.

The row is added successfully, but the cell value is not being written — the cell remains empty after the click. I've attached a demo that reproduces the issue.

Could you advise on the correct approach?

Thank you.

74. StringGrid.zip (3.7 MB)

2

What version do you use as I tested this here with the latest version and could not see an issue:

image
image500×324 1.63 KB

3

Hi Bruno,

I am using TMS Web Core 2.9.9.3. From TMS Dashboard, this is the lastest version.

4

I'd suggest to use the v3.0 beta. It has fixes & improvements in various components and main 'beta' work is centered around the new TWebDBDataGrid anyway, so should not harm as this particular component won't be used yet in production anyway.

5

Thanks for the suggestion.

We also observed that the checkbox click event was not firing in version 2.9.9.3. To test whether this was the cause, we downgraded TMS to 2.9.9.0, and the issues went away. BTW, I was wondering when an official V3 release is planned?

6

v3.0 release is planned for this week.

7

Hi Bruno,

After upgrading TMS to v3, I discovered an issue with TWebCheckBox. I've attached a test project to demonstrate it:

  1. Check the TWebCheckBox (which calls 'Hello')
  2. Click the 'Enable/Disable Checkbox' button to disable it

The problem is that when the checkbox is disabled, it works correctly, but it also becomes unchecked.

75. checkbox.zip (1.6 MB)

Do you have any suggestions to fix this?

8

We traced & solved this issue. We'll release 3.0.0.1 shortly with this fix

9

Hi Bruno,

After upgrading to TMS WEB Core V3.0.1, I'm still seeing a compile error related to TWebStringGrid. Steps to reproduce: drop a TWebStringGrid on a form, then change FixedCols to 0 in the Object Inspector. This triggers the following compile error:

image
image2395×178 15.8 KB

Any suggestions?

10

Thanks for reporting.
We could see & fix the issue. Next update will address this.
Set it at runtime as a workaround meanwhile.