As of the new Q3 release, one of my grids is virtually unusable because of a style change. I have a grid that has CanUserSelect set to false and IsReadOnly set to true--that way, a user cannot interact with the grid--and it's been perfect. However, in Q3, setting CanUserSelect to false now causes the grid to turn grey and go to a gradient 50% opacity (that's my guess). In any case, my user can barely see the grid now!
Why would you make this change? And if the change was necessary, what can I set to undo it?
Why would you make this change? And if the change was necessary, what can I set to undo it?
2 Answers, 1 is accepted
0
Hello Roger,
I was not able to reproduce the issue you described. Can you please send us a small application that demonstrates such a behavior. We could test it locally and provide you with an accurate solution.
Best wishes,
Vanya Pavlova
the Telerik team
I was not able to reproduce the issue you described. Can you please send us a small application that demonstrates such a behavior. We could test it locally and provide you with an accurate solution.
Best wishes,
Vanya Pavlova
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
0
Roger
Top achievements
Rank 1
Rank 1
answered on 30 Nov 2010, 06:54 PM
My apologies! It turns out that the real problem was that I had overlapping RadBusyIndicator objects wrapped around the grids (which I needed to be overlapped--one is always hidden) and one was getting revealed below the other. I've changed it to using one RadBusyIndicator instance for both grids.