10-09-2019, 04:22 PM
Hi Alexandre,
First of all, thank you for correcting the "IE error". We are waiting for the new version.
Secondly, I think we think differently about using IWGrid.
You are right about static rendering. But...
Your example:
<div ID="MYGRID">
<table id="TBLMYGRID">
<--! here goes the grid content -->
</table>
</div>
Other aspects:
- MYGRID has style (border, background, etc.) scaled to external components and TBLMYGRID content.
- TBLMYGRID is transparent, scaled to MYGRID.
- We want a responsive display
- We use the MYGRID == TBLMYGRID.parentNode relation in javascript.
Our well-used javascript functions for years have been disturbed by the appearance of new DIVs. But as I wrote, we have solved this problem.
We don't understand what the new div is good for? Mainly because sometimes it is, sometimes it is not.
If something has no advantage but caused some problems, the end result is negative.
Regards
brsoft
First of all, thank you for correcting the "IE error". We are waiting for the new version.
Secondly, I think we think differently about using IWGrid.
You are right about static rendering. But...
Your example:
<div ID="MYGRID">
<table id="TBLMYGRID">
<--! here goes the grid content -->
</table>
</div>
Other aspects:
- MYGRID has style (border, background, etc.) scaled to external components and TBLMYGRID content.
- TBLMYGRID is transparent, scaled to MYGRID.
- We want a responsive display
- We use the MYGRID == TBLMYGRID.parentNode relation in javascript.
Our well-used javascript functions for years have been disturbed by the appearance of new DIVs. But as I wrote, we have solved this problem.
We don't understand what the new div is good for? Mainly because sometimes it is, sometimes it is not.
If something has no advantage but caused some problems, the end result is negative.
Regards
brsoft