Best Way To Do This
-
I am working on this[] WPF application. Each time the user clicks Next I want to display the next view. Te areas in red will all have the header area at the top and the button area below. From what I can see it's impossible to subclass an XAML view, but I think I can do it with a template. I just don't know how. I'm open to suggestion. Thanks
Everything makes sense in someone's mind
-
I am working on this[] WPF application. Each time the user clicks Next I want to display the next view. Te areas in red will all have the header area at the top and the button area below. From what I can see it's impossible to subclass an XAML view, but I think I can do it with a template. I just don't know how. I'm open to suggestion. Thanks
Everything makes sense in someone's mind
It's not impossible to subclass XAML, it's fairly straightforward. In this case though, you simply need a ContentControl to host any one of a number of DataTemplates.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
-
It's not impossible to subclass XAML, it's fairly straightforward. In this case though, you simply need a ContentControl to host any one of a number of DataTemplates.
Forgive your enemies - it messes with their heads
My blog | My articles | MoXAML PowerToys | Mole 2010 - debugging made easier - my favourite utility
It's not impossible to subclass XAML, it's fairly straightforward. Got an example of how to do this? I Googled it earlier and didn't see much. In this case though, you simply need a ContentControl to host any one of a number of DataTemplates. Actually, if I put a ContentPresenter in the center cell of the grid, then the Next/Previous functions could simply add/remove whatever control goes there at that point.
Everything makes sense in someone's mind
-
It's not impossible to subclass XAML, it's fairly straightforward. Got an example of how to do this? I Googled it earlier and didn't see much. In this case though, you simply need a ContentControl to host any one of a number of DataTemplates. Actually, if I put a ContentPresenter in the center cell of the grid, then the Next/Previous functions could simply add/remove whatever control goes there at that point.
Everything makes sense in someone's mind
It looks like its just an inline wizard control. I'd go that route as that will help you keep your page logic seperated.
-
I am working on this[] WPF application. Each time the user clicks Next I want to display the next view. Te areas in red will all have the header area at the top and the button area below. From what I can see it's impossible to subclass an XAML view, but I think I can do it with a template. I just don't know how. I'm open to suggestion. Thanks
Everything makes sense in someone's mind
I think that you can do that using TabControl. Create tabcontrol template with invisible headers and navigate through it's Items when click Next or Prev. It will be like a wizard
-
I am working on this[] WPF application. Each time the user clicks Next I want to display the next view. Te areas in red will all have the header area at the top and the button area below. From what I can see it's impossible to subclass an XAML view, but I think I can do it with a template. I just don't know how. I'm open to suggestion. Thanks
Everything makes sense in someone's mind
Looks like a prime candidate for the Prism frameword (previously Composite Application Lib)
C# has already designed away most of the tedium of C++.
