Inconsistent error notification behavior between "Full Row" and "Cell" selection units

5 posts, 0 answers
  1. Ireney
    Ireney avatar
    8 posts
    Member since:
    Oct 2015

    Posted 29 Dec 2015 Link to this post

    If "Full Row" selection unit is used, and particular field has an error, the row header displays an error icon summarizing the errors when hovered over (see attached "error - full row selection unit.jpg"). This is not the case when "Cell" is the selection unit (see "error - cell selection unit.jpg").

    Do I need to set something to enable the same behavior, or is this a bug?    

    I am using trial version (2015.3.1104.45)

  2. Martin
    Admin
    Martin avatar
    1099 posts

    Posted 31 Dec 2015 Link to this post

    Hi Ireney,

    Thank you for the attached images and the description. We will contact you in few days with more information on the matter.

    Regards,
    Martin
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  3. UI for WPF is Visual Studio 2017 Ready
  4. Dilyan Traykov
    Admin
    Dilyan Traykov avatar
    368 posts

    Posted 04 Jan Link to this post

    Hello Ireney,

    I'm afraid there is no straightforward way to set this.

    This behaviour is expected as when the selection unit is "Cell", each cell is responsible for displaying its own validation errors.
    With SelectionUnit="FullRow", however, each row displays all the errors it has aggregated and thus, the indicator is present.

    You can use Implicit Styles and set the visibility of the ErrorIndicator to Visible in order to make the Indicator visible when the SelectionUnit is Cell.

    Regards,
    Dilyan Traykov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
  5. Ireney
    Ireney avatar
    8 posts
    Member since:
    Oct 2015

    Posted 04 Jan Link to this post

    Hi Dilyan,

    If this is intended behavior, I think this is not an appropriate solution for a number of reasons:

    • One major reason is that it introduces inconsistent behavior that may be confusing to the users. 
    • Second major problem is usability: if my grid features many columns, or requires users to scroll, the user will not know what the issue is. The user will be forced to scroll to the offending cell to determine the error, rather then having access to those errors readily available at the header.

    Regarding ErrorIndicator, I am using implicit styles in my proof of concept apps, however I am still unfamiliar with the structure of your templates, and it is unlikely that I will have much time to fully familiarize myself with it as part of my evaluation.  I quickly look and tinkered with GridViewCellCoreValidationTemplate in Telerik.Windows.Controls.GridView.xaml, but none of the changes I introduce to it, whether alternate border thickness or border brush for instance, seem to have an effect.  Could you point me in the right direction?

  6. Dilyan Traykov
    Admin
    Dilyan Traykov avatar
    368 posts

    Posted 05 Jan Link to this post

    Hello Ireney,

    I took a detailed view of our source code and I can confidently state that this behaviour is by design and we're not planning a change in it.

    However, I've attached a sample project showing you how you can achieve the desired effect with a custom column. You can further modify it to your liking.

    Please let me know if this helps.

    Regards,
    Dilyan Traykov
    Telerik
    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Feedback Portal and vote to affect the priority of the items
Back to Top
UI for WPF is Visual Studio 2017 Ready