On a grid, I set CanUserSelect to false. It works fine for mouse selection (the user cannot select a row with the mouse) but not with keyboard arrow keys.
Let me describe how to reproduce it: if you click on the grid (nothing is selected) but the grid gets the focus. Then, you use the arrow keys (up or down) and it selects the row just where you clicked (and not where the last selection was set in code)!
So, not only the user can select a row with the keyboard but "something" is also selected when clicking! Even if the selection doesn't change, the row that was clicked is still saved somewhere.
Is this a normal behavior? Am I missing an option on the grid to disable the keyboard select?
If it's a bug, do you have a workaround and when will it be corrected?
Best regards,
Daniel
EDIT: I forgot to specify that we use the Q1 2010.
5 Answers, 1 is accepted
We are aware of this issue we are currently working on a fix. I will notify you as soon as this issue is resolved.
Thank you very much for your patience.
Regards,
Milan
the Telerik team
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 Public Issue Tracking system and vote to affect the priority of the items.
I have a question regarding the usage of the CanUserSelect property. We would like to get more information about scenarios that require the selection to be turned-off. Are you using CanUserSelect because you would like to disable the selection highlights that are shown by default or because the user should not be able to modify the SelectedItem property and SelectedItems collection?
We would really appreciate it if you could spend some time to share more information about the requirements that led you to use CanUserSelect.
Thank you for your time.
Best wishes,Milan
the Telerik team
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 Public Issue Tracking system and vote to affect the priority of the items.
In our case, we don't want the user to be able to modify the SelectedItem property and SelectedItems collection.
The selection is done in code behind, based on other options previously selected in the window.
For example, we have to grids. The first one contains a list of errors, the second one contains a list of lines. Each error in the first grid concerns one (or several) lines in the second grid.
So when the user selects an error in the first grid, we want the appropriate lines to be selected in the second grid. Of course, the second grid should not be selectable by the user.
That's what we expect from CanUserSelect.
(In my own opinion, an option to disable the selection highlights should get another name, such as IsSelectable).
Best regards,
Daniel
Thank you very much for the clarifications.
We have fixed the problem in our latest Internal Build (will be available later today) and users will not be able to change the selection when CanUserSelect is false.
I have updated your Telerik points.
Sincerely yours,
Milan
the Telerik team
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 Public Issue Tracking system and vote to affect the priority of the items.