Hi Stephen,
Thanks for response.
Unfortunately neither of the methods you mentioned is useful for me:(
1. http://www.telerik.com/DEMOS/ASPNET/Prometheus/Controls/Examples/Integration/GridAndSplitterResizing/DefaultCS.aspx?product=splitter
This method (setting PageSize programmatically) is useless in my case - I have variable height rows (templated) and so have to use scrolling, as I mentioned before.
2. Setting height to eg. 75% makes layout look awful:
First - the pager is not always on the bottom of a container and the container filling depends on current window size - in higher resolutions there is a lot more whitespace below grid than in lower resolutions. This is why I want the grid to fill whole container - my application will be used on res's from 800x600 to 1920x1200.
Second - the CommandItem height problem still exists, but in other form. It looks like the border of a grid's content has proper height (75% of a container), but the grid itself is still higher (75% + CommandItem height). The effect is that bottom part of the border is not below last item (between pager and content as its should be), but it is placed ON the last item (because the grid is sligtly higher)... I think there's some rendering problem when using height in %'s and CommandItem
Third - it works only on IE (checked under IE7 - FF completely ignores the percentage and displays the grid about 200px high...)
You can simply repro this behavior (RadSplitter + RadGrid + CommandItem + Scrolling + Static Headers + Height 75% + eg. Vista skin). I can also send a screenshot to visualize the problem.
Isn't there any other way to make this settings work (on both IE7 and FF)? Maybe some custom CSS styling, wrapping the control in some way or something? I've searched all forums, docs and demos and haven't found any useful solution...
BTW - I understand the rendering method, but, logically thinking,
shouldn't this be considered as a bug? RadGrid is thought to be one control (including CommandItem, Pager, Headers, Footer and content), so it's Height property should apply to the control as a whole, without forcing the end-user to know the underlying rendering system... In other words - it's just a bit misleading.
One more thing - is RadPane OnClientResized event fired when resizing browser window?
Regards,
Piotr