Setting a TcxGridDBLayoutView's Controller.Customization to True trows an Integer Overflow

The hotfix did fix the problem. Thanks.

After installing the latest version of DevExpress (14.2.4), I tested the customization of a GridDBLayoutView and it's still throwing a message : Project (project name here) raised exception class EIntOverflow with message "Integer overflow".
The problem comes from dxComCtrlsUtils.pas in the following procedure :
procedure cxTreeViewGetSelection(ATreeView: TTreeView; AList: TList);
var
 I: Integer;
begin
 for I := 0 to ATreeView.SelectionCount - 1 do
   AList.Add(ATreeView.Selections[I].Data);
end;
In the particular case, ATreeView.SelectionCount is 0 so ATreeView.SelectionCount - 1 equals -1 and the for loop tries to loop from 0 to -1 thus throwing the exception.
This is the second time I report this problem (see above for solution).
Just in case, I suggest you to change your code with the following code :
Procedure cxTreeViewGetSelection(ATreeView: TTreeView; AList: TList);
var
I: Integer;
begin
 if ATreeView.SelectionCount > 0 then begin // Check if larger than 0
    for I := 0 to ATreeView.SelectionCount - 1 do begin
       AList.Add(ATreeView.Selections[I].Data);
    end;
 end;
end;
BTW, the hotfix did fixed some issues, but it failed to fix this one.
Regards,
Stephan St-Denis

Hello Stephan,

Would you please provide us with the instruction on how to reproduce this issue with your demo?

I can't reproduce it in the small, sample program I initially sent but here's a bigger project, based on our REAL program in which we encountered the problem when we installed DevExpress 14.2.3.
The program is compiled, but I will also send you the source code. The program uses the Advantage Database Server. I converted the sample program to use the Local Server.

Here's the source code.

Hello Stephan,

I am afraid that I was not able to compile this project because I do not have Advantage Database controls installed on my side. Are they essential to reproduce this error? If they are not, would you please perform the following actions to localize the problem? Reset all event handlers in your application. If the problem is gone, set them back one by one, and see when the problem returns. If this does not help you, try removing all controls one by one, and test your sample at each step, until the problem is gone. As a result, you will have a small sample illustrating the problem.
To provide required data you can load it to ClientDataSets or TdxMemdata (use their "Assign Local Data…" option). This will allow us to review your sample on different machines without using 3rd-party components.