After a lot of testing together with zryip theSlug who has built DGH (DataGrid Helper) the cause of the problem was found.
This is what i have been told.
So, the problem is exactly located in the fixed row height property. In your datagrid table it was set to false, and for any new fresh datagrid it is set to true by default.
When you created the datagrid for scratch you probably set the fixed row height to false.
This is the solution you can share in the forum. The cause is DGH is displaying by mistake the property for tables and for forms. DGH will be updated for removing this option for tables.
2. The datagrid library is taking care of variable row heights only for datagrid form not for table. The issue we have with the "fixed row height" property seems to confirm that. And when we are observing the property in the inspector, it only appears for datagrid form.
I've never noticed that when I built DGH. In a next version I will display the property only for forms.
So for a table style datagrid keep the fixed row height property to true.
If all else fails you might want to try to do the following (not sure it will work in your case)
Do not forget to save the script you have got within the DataGrid somewhere else. Will probably save a lot of time later!
Part 1 (Clone part of your DataGrid to a new DataGrid)
- set up a new DataGrid.
- Select (have focus on) the DataGrid with the issue
- In DGH open the "Mimetism" topic
- Add your project datagrid in the "cloning chamber" by clcking on the button with the '...' and then select '' Add in chamber
- Select the fresh datagrid in the new test stack
- In DGH, click on the clone button 'Clone properties & Template'.
- Select the option "Datagrid columns" and only this one (without template and properties)
- Validate with the green button. This will clone the columns only
Part 2 Clone the settings of your new DataGrid back to your DG with the issue.
- Now do the same action backwards but now select the option:
* "Datagrid columns"
with template and properties).
* and the option DataGrid properties.
The original datagrid is now based on the fresh datagrid properties. Maybe this helps
DO THIS AT YOUR OWN RISK. So making a backup copy of the stack before is a wise thing to do !! I got a few errors in DGH so I had to save the stack and restart Livecode after which I could do Part 2.
Regards,
Paul