12.1p+ ListGrid column width differences depending on canEdit

[Blama]

Hi Isomorphic,

playing with this sample (v12.1p_2025-11-27, v13.1p_2025-11-27) I found a strange effect. ListGrid column widths differ severely depending on the presence of canEdit.
1st ListGrid has canEdit:true, the 2nd one does not.

isc.VLayout.create({
    width: "100%",
    height: "100%",
    members: [
        isc.ListGrid.create({
            ID: "dsListGrid",
            canEdit: true,
            width: "100%",
            height: "100%",
            autoFetchData: true,
            dataSource: "supplyItem"
        }), isc.ListGrid.create({
            ID: "dsListGrid2",
            width: "100%",
            height: "100%",
            autoFetchData: true,
            dataSource: "supplyItem"
        })
    ]
});

Best regards
Blama

[Blama]

More minimal testcase without data:

isc.VLayout.create({
    width: "100%",
    height: "100%",
    members: [
        isc.ListGrid.create({
            ID: "dsListGrid",
            canEdit: true,
            dataSource: "supplyItem"
        }), isc.ListGrid.create({
            ID: "dsListGrid2",
            dataSource: "supplyItem"
        })
    ]
});

[Isomorphic]

It's expected that default sizes would differ due to our heuristics that try to leave room for editors in certain fields. In this case, Next Shipment gets squeezed more than it should, but that basically has to do with Units being given too much space, not to a problem in the heuristics per se.

[claudiobosticco]

Hi, maybe it's related to this https://forums.smartclient.com/forum...113#post276113

[Blama]

Hi Isomorphic ,

OK, if it works as designed that is fine for me as well. Just wanted to point out the observation.
I agree that taking editor widths into consideration makes sense.

Thank you & Best regards
Blama