C# DataGridView - disabling rows?

[gumbald]

Not had much experience of the DGV, but think I'm using it outside of it's intended scope and pushing it too far, so open to suggestions for alternatives if someone can think of one...

I populate it with a set of items of a known maximum size, which worked fine when the description for each item belonged to the same row in the view. This meant I could just hide the rows when not applicable.

However, I now want to pull the descriptions out into a static list and have a number of DGVs showing applicable items in multiple lists based on other conditions. This creates the problem of not being able to hide rows in the variable columns, as they then wouldn't correspond with the description in the static list.

Soooo, is there a way of disabling a row (as in greying it out) or preventing the checkbox in the row from being selected? I can't seem to seem to find a nice method for either of these solutions...?

Let me know if I'm not making any sense!

 

[gumbald]

Currently, this is what I have - the description field is part of the same DGV, so in cases where certain rows do not appear everything still lines up:

However, I'd like to extend it to have multiple DGVs containing variations of the same data but with a static description field. Obviously here, removing rows causes them to shift up and therefore not line up with the description:

So I'm looking at some way of just 'disabling' the rows rather than removing them...

 

[gumbald]

so hang on. You are putting 2 DGV's 'next' to each other on the page to give the illusion of 1? So the deletion of a row from one DVG scews the grid data?

In a sense, yes. I'll want more DGVs, some are only applicable under certain conditions... But it's far easier to hide a whole DGV obviously.

If that's the case the it would make far more sense to create a single DGV with extra columns and then do some logic in the background to populate.

This is the slightly roundabout way I was looking to avoid, yet obviously feasible. If it's the best option I'll have to go for that.

Any chance of seeing the code which populates the DVG(s)?

I might confuse the situation more with that. Basically, it's not dynamic, I create the DGV with a list of known values, then 'hide' certain rows under certain conditions. There's no database links or such, the entries have fixed values.

 

[gumbald]

Ok, things are a lot clearer now. But why you are doing things this way still has me a little confused - are you trying to hack a quick demo together, or are you just starting out programming?

I was testing the water as to whether it would be easy enough to morph from my previously working method into using separate grids. I know the grid perhaps isn't the best tool for the situation anyway. So in a sense, a demo.

Have you thought about the logic needed to find which rows to hide? I would think if you have 3 or 4 DGV's next to each other the logic needed to line the rows up would be a little intense to say the least.

The logic to find which rows to hide already exists, I'd just be extending it under certain conditions.

From a programming pov it makes far more sense to use a single DGV and do the logic before binding the data to the DGV, preferably using a custom data type.

This does look like the best way it seems. That's fine. I suspected as much, just needed someone to make me see sense I suppose. I'll start making some bigger changes.