grid AdvanceInsert, AdvanceOnEnter bugs

TMS VCL UI Pack 10.7.4.1 version is in use.

You have set the grid to AdvanceInsert=true and AdvanceOnEnter=true.
If the first column is fixed=true, the program goes down in stack overflow.
If the last column is fixed=true and width=0, no row is created.
If the last column is fixed=false, two rows are created.
If you set the first column to fixed=false, the last fixed=true, and width=1, only one row is generated at the end, but if you enter in the last column of the row instead of the last row, the row is created.
This version will continue to have bugs.

I assume you refer here to TAdvColumnGrid?
If not, what exact grid is referred to and how is it setup to make the first column fixed as I could not see both with TAdvColumnGrid & TAdvStringGrid a stackoverflow.

Test setup on default TAdvColumnGrid:

  AdvColumnGrid1.Navigation.AdvanceInsert := true;
  AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
  AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];
  AdvColumnGrid1.Columns[0].Fixed := true;
// tested with & without these extra settings
  AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Fixed := true;
  AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Width := 0;

Use the TAdvColumnGrid.

  1. The result of the setup.
    AdvColumnGrid1.Navigation.AdvanceInsert := true;
    AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
    AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];
    AdvColumnGrid1.Columns[0].Fixed := true;
    image

  2. The result of the setup.
    AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Fixed := true;
    AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Width := 0;
    The row is not created.

  3. The result of the setup.
    AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Fixed := true;
    AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Width := 1;
    The row is created.
    However, if you type enter in the row instead of the last row, the row is created at the end.

  4. The result of the setup.
    AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Fixed := false;
    AdvColumnGrid1.Columns[AdvColumnGrid1.Columns.Count - 1].Width := 0 or 1;
    Two rows are created each.

We released v10.7.5.0 with improvements. Can you check with this update?

AdvColumnGrid1.Navigation.AdvanceInsert := true;
AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];

  1. The result of the setup.
    RowCount-2, RowCount-1 both create a new row.
    The symptoms are the same in all states.

  2. The result of the setup.
    AdvColumnGrid1.Columns[0].Fixed := false;
    The cursor moves to the last row.

  3. The result of the setup.
    AdvColumnGrid1.Columns[0].Fixed := true;
    If you type enter in RowCount-1, AdvColumnGrid1.Columns.Count -1, the cursor does not move to the last row after row creation.
    If you type enter in RowCount-2, AdvColumnGrid1.Columns.Count-1, stack overflow occurs.

  1. Could be reproduced & fixed
  2. Could not be reproduced
  3. Could not be reproduced

Tested with default grid on the form and

case 1:

AdvColumnGrid1.Navigation.AdvanceInsert := true;
AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];

case 2:

AdvColumnGrid1.Navigation.AdvanceInsert := true;
AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];
AdvColumnGrid1.Columns[0].Fixed := false;

case 3:

AdvColumnGrid1.Navigation.AdvanceInsert := true;
AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];
AdvColumnGrid1.Columns[0].Fixed := true;

case 1:

AdvColumnGrid1.Navigation.AdvanceInsert := true;
AdvColumnGrid1.Navigation.AdvanceOnEnter := true;
AdvColumnGrid1.Options := AdvColumnGrid1.Options + [goEditing];
AdvColumnGrid1.Columns[0].Fixed := false or true;

case2, case 3:
The settings you understand are correct.

Ok, then after fixing 1), we could not see any further problem.

Did you say that it was solved in v10.7.5.0?
A bug that occurred while testing after updating the v10.7.5.0 version.

The release 10.7.5.0 was yesterday. I looked at your problem today and replied today that a fix was done, so this fix is NOT in 10.7.5.0

Yes, I got it.
The translator is not perfect.