WEI

Hi, Boki

I guess you have a serious bug in TNextGrid with TNxTreeColumn when using PAGEDOWN and PAGEUP button, here is how to reproduce it:

Create a clean form, add a NextGrid control (make the visible row count = 10 rows) and with one TNxTreeColumn and one TNxTextColumn, add a button on the form, at the on button click event, adding the following code



When if the first row is expanded, Press PAGEDOWN button will goes to 10th row, which is good. but when the first row is shrink(all its child rows are all invisible), then press PAGEDOWN, it will goes to/8th rows. so if adding more child rows, press PAGEDOWN will goes to row of VISIBLECOUNT - child count of first row. so you can image if the child row of the first row exceed the total of visible row count, What will be happend?

so I would assume that pressing UP ARROW and DOWN ARROW would have the same problem.

so please give this a quick fix, we can not afford this kind of bug to give to our customers.

Why don't you fully test your grid before make a new release?

Regards,

WEI

HI, Boki

I guess I found a bug in TNextGrid.AddRow:



If you add a 20 rows to an empty grid (GridLinesStyle = lsFramed and goGrid = True) by calling AddRow(20), then RefreshRowGrid(-1), which cause List Index out of bounds: -1?

Any ideas how to fix?

Regards,

WEI

Hi, boki

In the method TNxCustomGrid.UpdateArrows of NxCustomGrid unit, line 1678:



since both statement in the case TargetColumn.Location is the same, so will it be (remove case):



or is it just missing something in the original code?

Regards,

WEI

HI,

Just bought NextGrid Suite yesterday. I found a serious problem, The NextGrids didn't work properly in inherited forms. The grids were totally screwed up if changing any of the properties of the grids which in the inherited forms for existing columns at design time. Its a stopshow to us now. Any chance to have a quick fix in the next release?

Thanks

WEI