Greetings,
I've read on some old forum threads that a RadGrid's ClientSettings must set UseStaticHeaders to "true" in order for FrozenColumnsCount > 0 to take effect.
We've also observed this behavior in our use of the ClientSettings.
1) Please confirm : Must UseStaticHeaders be set to "true" in order for FrozenColumnsCount > 0 to take effect ?
2) If #1 is confirmed, Why ? Why was the control designed this way ?
3) If #1 is confirmed, is this strange, undocumented dependency already fixed in the 2013 release(s)? If not, will it be decoupled soon?
I've read on some old forum threads that a RadGrid's ClientSettings must set UseStaticHeaders to "true" in order for FrozenColumnsCount > 0 to take effect.
We've also observed this behavior in our use of the ClientSettings.
1) Please confirm : Must UseStaticHeaders be set to "true" in order for FrozenColumnsCount > 0 to take effect ?
2) If #1 is confirmed, Why ? Why was the control designed this way ?
- This dependency is not mentioned or alluded to in the Telerik documentation of the GridScrolling memebers http://www.telerik.com/help/aspnet-ajax/allmembers_t_telerik_web_ui_gridscrolling.html
- This dependency doesn't seem to make sense from a technical perspective either; in fact, it seems like it'd be harder (more complex) for Telerik to enforce/create the frozen column behavior in a UseStaticHeaders="True" scenario as compared to a UseStaticHeaders="False" due to the way UseStaticHeaders actually renders the RadGrid HTML (which is in separate HTML tables).
- This dependency doesn't seem to make logical/ use case perspective. Isn't a common scenario one where a user doesn't want the headers fixed but does want a column or two fixed ?
3) If #1 is confirmed, is this strange, undocumented dependency already fixed in the 2013 release(s)? If not, will it be decoupled soon?