Question

I feel like there’s something about grids that I’m missing, but I can’t find it through Googling around.

For example, I want to be able to declare ten rows with ten columns, populate them with data, and then later realize that I don’t need row 3, and be able to quickly reformat it. I’m not speaking of doing this programmatic, but while redesigning the project. One way that this could be handled in theory would be HTML’s manner of deleting a set of <tr></tr>s. This would be limited to rows, obviously. Another way might be the ability to give each column a name, such as “CityColumn,” “StateColumn” (or named whatever else depending on the use of Grid), and then simply deleting the column’s definition and all elements declared to exist in the column.

As is, if you delete any given row or column, you must go to each and every element that appears in a later row or column and change the row or column’s number. It seems like there should be a better way to use XAML’s grid that I’m not making use of.

While I lack a clear question that I can define, it can be said that I’m looking for best practices and/or any tips and tricks to make Grid easy to modify it and its contents and, in general, provide upkeep for.

Either explanations or links to learning resources about XAML’s Grid would be welcome.

Answer 1

I would recommend what Jeff Mercado said: ListView with GridView as its View. The columns of that view can have headers, and if you remove an item the respective row is gone.

Also you can optimize the Grid maintainability, if you intend to stick with that, by using named references rather than indices, so if you remove one row that becomes much easier.