08-18-2019, 10:24 PM
(This post was last modified: 08-18-2019, 10:27 PM by DanBarclay.)
Interesting that I've got a IWDBGrid on one of my forms. I have only top/left anchors set.
I've recently found that if I reduce the number of rows it will dramatically increase the rowheight as well. But, if I start it with one row the height is correct.
Also find that changing the number of rows (change dataset query, in async event) so that:
Initially too many for the grid, sets a scrollbar as expected.
Then, Change dataset query to reduce the rowcount to 2 or 3 rows, rowheight increases (apparently fills the grid region).
Then, Increase rowcount to approximately the region size, rowheight reduces again to normal size.
Then, Increase rowcount to many more, the grid overflows the region and continues on the page well beyond the footer (footer is in template).
I haven't changed this in a very long time so haven't looked at anything cute I might have done in the code but I don't recall this behavior when I was working on it. It's not a scenario I routinely run into so not sure about behavior change, but was easy for me to try and simulate the situation above.
Now running 15.1.2 in XE2.
I'm not sure this is related to the issue above but let me know if you need anything from me. I will update to 15.1.3 when I get a chance.
Dan
I've recently found that if I reduce the number of rows it will dramatically increase the rowheight as well. But, if I start it with one row the height is correct.
Also find that changing the number of rows (change dataset query, in async event) so that:
Initially too many for the grid, sets a scrollbar as expected.
Then, Change dataset query to reduce the rowcount to 2 or 3 rows, rowheight increases (apparently fills the grid region).
Then, Increase rowcount to approximately the region size, rowheight reduces again to normal size.
Then, Increase rowcount to many more, the grid overflows the region and continues on the page well beyond the footer (footer is in template).
I haven't changed this in a very long time so haven't looked at anything cute I might have done in the code but I don't recall this behavior when I was working on it. It's not a scenario I routinely run into so not sure about behavior change, but was easy for me to try and simulate the situation above.
Now running 15.1.2 in XE2.
I'm not sure this is related to the issue above but let me know if you need anything from me. I will update to 15.1.3 when I get a chance.
Dan