I have a grid that displays cells containing check boxes. When I set certain rows to Disabled or NoEdit, the user can still 'uncheck' checked items on the disabled cells/rows. They cannot check but they can uncheck.
Hi Amber,
Can you post a small sample project demonstrating this behavior? I've never heard of a problem like this in the grid - at least not that I remember.
I sent you a screenshot to demonstrate the behavior. Can't you test it out based on that? The behavior occurs when the user clicks on the checkbox label. Clicking the label unchecks the checkbox but it will not check back again.
Hi,
There's not a whole lot I can do with a screen shot. In my experience, when trying to duplicate some strange behavior, screen shots are almost always pretty useless. The only time they help is if there is some visual problem occurring and it happens to be an issue I have seen before.
A screen shot doesn't tell me how you got a checkbox and text in the same cell - or even if they are in the same cell. They could be in two different cells for all I can tell here. It also doesn't tell me how you are disabling the checkbox in code. I can't see the code and I can't debug it. A screen shot doesn't tell me what version of the controls you are using, nor what version of Visual Studio your application is in. So without knowing how you set this up, there's no way I can guess why it's not working or try to duplicate it in any meaningful way.
Anyway, I tried this out in the simplest way I know how, using an UltraCheckEditor control and, of course, it works just fine for me. I have attached my sample here.
So there must be some other factor at work in your code with the way you set this up. If you can post a sample project demonstrating the issue, I would be happy to look into it and tell you what wrong. But without a sample to debug, there's not much I can do.
I understand, Mike. Thanks for looking into it the best you could.
As for my situation, I had a deadline to meet, so I ended up cancelling the BeforeCellChanged event when the unwanted behavior I mentioned was about to occur. I'm not sure why that event even fires when the row the cell is located in is set to Activation.Disabled but it worked and took care of my immediate issue.