Lightweight Templates and RowIndicatorVisibility property

[Jeff]

In the online doc topic on "Lightweight Templates" here:

http://www.telerik.com/help/wpf/gridview-overview-lightweight-template.html

There is a note that states:

"Please set the RowIndicatorVisibility property of the RadGridView to Collapsed to avoid any visual differences between the row's headers and cells."

It's unclear to me what this has to do with the Lightweight templates and why it's necessary to Collapse the RowIndicator?  Also, I notice that in the last screenshot shown in the above-linked topic, the RowIndicator is clearly visible (so, not collapsed)...

In my case, I'd like to use the lightweight templates (with validation) for performance, but I need the RowIndicator column to be visible in order to select entire rows for various editing functions.  I've activated the lightweight templates, but have not collapsed the row indicator as suggested.  I don't see any issues with this combination, but wondered what I might be missing?

Thanks for any clarification on this topic.

Jeff

[Vanya Pavlova]

Hi Jeff,


Thank you for contacting us!

Lightweight templates are plain templates for these elements with limited set of features.
In the core styles you have hover, selection, grouping, core validation styles include validation. 
All of these are implemented with limited set of visual elements, which speeds up the performance of the grid. The rest features as part of standard templates are excluded. 
Since we provide two separate styles for rows, please check the following note:

GridViewRowCore - this style do not contain row indicator. The RowIndicatorVisibility using this style should be set to Collapsed, because it leads to misalignment among the rows and gridview's header. 

GridViewRowCoreValidation- this style contains row indicator, which you may use to perform validation. 


May you verify how this works for you? 


Regards,
Vanya Pavlova
Telerik

[Jeff]

Vanya,

Thanks for the input.  I understand the purpose of the lightweight templates and they should work well for my usage case.  The two notes you added to your response make perfect sense and definitely clarify my initial question.  However, unless I'm mistaken, those notes are not part of the mentioned documentation topic.  I'd suggest they (or something like them) should be added to the docs for additional clarity.

Thanks again.

Jeff

[Dimitrina]

Hello,

Thank you for your feedback. The documentation will be updated accordingly.

Regards,
Didie
Telerik