We're currently evaluating your grid (which is great by the way) and I have a few questions regarding hierarchies:
1. Is it possible to remove (or at least reduce the size of) the border around child grids? The default one has a thick blue border which is eating up a lot of screen space.
2. Rows in the grid are typically highlighted when you move the mouse over them, but the last row hovered over in a child grid stays highlighted when you move the mouse down and out of the child grid. It's not such a big issue, but if that row has the background colour changed for business reasons, the highlight remains which hides the background colour. If you move the mouse up and over the child column headers first the highlight is removed as normal. Is this a bug?
3. Am I missing something or is there no way to bind hierarchies of business objects with self contained collections? For example, I have a collection property on my view model called Customers. This model works great in your WPF grid, but for the WinForms case I had to create two separate collections in the view model for customers and orders, add a CustomerKey property to the Order class and then specify a GridViewRelation between them.
1. Is it possible to remove (or at least reduce the size of) the border around child grids? The default one has a thick blue border which is eating up a lot of screen space.
2. Rows in the grid are typically highlighted when you move the mouse over them, but the last row hovered over in a child grid stays highlighted when you move the mouse down and out of the child grid. It's not such a big issue, but if that row has the background colour changed for business reasons, the highlight remains which hides the background colour. If you move the mouse up and over the child column headers first the highlight is removed as normal. Is this a bug?
3. Am I missing something or is there no way to bind hierarchies of business objects with self contained collections? For example, I have a collection property on my view model called Customers. This model works great in your WPF grid, but for the WinForms case I had to create two separate collections in the view model for customers and orders, add a CustomerKey property to the Order class and then specify a GridViewRelation between them.
public class Customer
{
public int CustomerKey { get; set; }
public string Name { get; set; }
public IList<
Order
> Orders { get; set; }
}
public class Order
{
public int OrderKey { get; set; }
public decimal Price { get; set; }
}