You could make your grid always contain 3 rows and 3 columns. When you are using "rows", you would need to add Grid. ColumnSpan="3 (in order to keep this looking the same), and when transposed, use RowSpan In order to do the transposition, handling this in code is most likely the simplest option.By calling Grid.
GetRow SetRow etc on your items, you could easily do the transposition To avoid putting this into the code behind, you could make an attached property which worked on the grid itself. This would allow you to have the property bind to a boolean or enum in your ViewModel, and perform the transposition at runtime based on business logic.
You could make your grid always contain 3 rows and 3 columns. When you are using "rows", you would need to add Grid. ColumnSpan="3" (in order to keep this looking the same), and when transposed, use RowSpan.In order to do the transposition, handling this in code is most likely the simplest option.
By calling Grid. GetRow/SetRow/etc on your items, you could easily do the transposition.To avoid putting this into the code behind, you could make an attached property which worked on the grid itself. This would allow you to have the property bind to a boolean or enum in your ViewModel, and perform the transposition at runtime based on business logic.
If you can swap out the Grids for StackPanels test1 test1 test1 Then you can make use of this converter public class InverseOrientationConverter : IValueConverter { public object Convert(object value, Type targetType, object parameter, CultureInfo culture) { if (!(value is Orientation)) throw new ApplicationException(); Orientation orientation = (Orientation)value; if (orientation == Orientation. Horizontal) return Orientation. Vertical; return Orientation.
Horizontal; } public object ConvertBack(object value, Type targetType, object parameter, CultureInfo culture) { throw new NotImplementedException(); } }.
If I did that, I would have to set the width and height of individual controls explicitly or the column arrangement of the controls would not be uniform. – I.M. Feb 16 at 17:07.
You could make your grid always contain 3 rows and 3 columns. When you are using "rows", you would need to add Grid. ColumnSpan="3" (in order to keep this looking the same), and when transposed, use RowSpan.
In order to do the transposition, handling this in code is most likely the simplest option. By calling Grid. GetRow/SetRow/etc on your items, you could easily do the transposition.
To avoid putting this into the code behind, you could make an attached property which worked on the grid itself. This would allow you to have the property bind to a boolean or enum in your ViewModel, and perform the transposition at runtime based on business logic.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.