You could use SystemColors to make the control background colour match (rather than being white) I don't understand why you want to put one grid on top of another though. In WPF you generally use a single grid to stack multiple visual elements within one region. Can you explain why you want to hide things in the background with foreground elements?
It sounds a little like you're implementing a tab control -- switching between pages of controls depending on focus. Have you experimented with the new TabControl? I'm moving from WinForms to WPF development wherever possible and have found that in doing so it's taken some readjustment.
WPF has a completely different way of laying things out and now that I'm more comfortable with it, I think it's superior. I'm guessing you just need to ride the learning curve a little longer Hope that helps EDIT: In response to your comment, I imagine you can have a tab control without tabs, though I haven't tried it myself (might be worthy of another question on SO). Tab controls are headered controls, meaning that they have a header item and a content item.In this case, the header is the tab button, the content is the page item.
You can specify a ControlTemplate that details how these items should be displayed relative to one another Interestingly, many other types of common GUI element are also headered controls: Menu items The menu item text/icon is the header, and the optional submenu is the content Tree view Each node is the header, and optional children are within the content Group box The header is, well, the header and the content is, well, the content :) Note that in the case of menu items and tree views, the type may recursively nest within itself. This is quite elegant and can give some wildly different presentation options over the same logical model with only changes to the control template For more information read about HeaderedContentControl and HeaderedItemsControl.
You could use SystemColors to make the control background colour match (rather than being white). I don't understand why you want to put one grid on top of another though. In WPF you generally use a single grid to stack multiple visual elements within one region.
Can you explain why you want to hide things in the background with foreground elements? It sounds a little like you're implementing a tab control -- switching between pages of controls depending on focus. Have you experimented with the new TabControl?
I'm moving from WinForms to WPF development wherever possible and have found that in doing so it's taken some readjustment. WPF has a completely different way of laying things out and now that I'm more comfortable with it, I think it's superior. I'm guessing you just need to ride the learning curve a little longer.
Hope that helps. EDIT: In response to your comment, I imagine you can have a tab control without tabs, though I haven't tried it myself (might be worthy of another question on SO). Tab controls are headered controls, meaning that they have a header item and a content item.In this case, the header is the tab button, the content is the page item.
You can specify a ControlTemplate that details how these items should be displayed relative to one another. Interestingly, many other types of common GUI element are also headered controls: Menu items - The menu item text/icon is the header, and the optional submenu is the content Tree view - Each node is the header, and optional children are within the content Group box - The header is, well, the header and the content is, well, the content :) Note that in the case of menu items and tree views, the type may recursively nest within itself. This is quite elegant and can give some wildly different presentation options over the same logical model with only changes to the control template.
For more information read about HeaderedContentControl and HeaderedItemsControl.
In terms of functionality, it is like a tab control, but which tab the users sees is actually based on context. Its your standard windows explorer style application, tree view of objects on the left, content pane on the right. – Jonathan Beerhalter Jan 17 '09 at 18:11.
You could use the following: This will respond to changes in the system colors on the fly (the DynamicResource does this).
1 Use StaticResource for reduced overhead with the downside that your application won't update if it's running while someone changes the system's colours. – Drew Noakes Jan 17 '09 at 16:54 This is one of the cases where DynamicResource is applicable while I agree with you that Static is usually to be preferred. – denis phillips Jan 17 '09 at 18:11.
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.