index > Windows Presentation Foundation ("Avalon") > Custom Window

Custom Window

I am creating a custom window that looks similar to the Office 2007 UI. I was able to create an appropriate ControlTemplate/Style with dragging and "Close", Maximize/Minimize buttons etc... But here' the question: What's the best approach to have it encapculated in the separate class/component so I can easily re-use this style for other windows in the app?

-- Alex Yakhnin, Device Application Developer MVP | http://blog.opennetcf.org/ayakhnin

AlexY

You could put the template and style into the App's resources, without a x:Key, and set the TargetType to {x:Type Window} to make every window in the app automatically use that style. Is that what you're looking for?

Josh Smith - http://www.infusionblogs.com/blogs/jsmith/default.aspx

Josh Smith

Yeah... this is what I've done as well, but how do I go about events? For example, I have the LeftButtonDown events for 3 elements that are doing window dragging, closing and maximizing and in the App.xaml.cs we don't know about the window's instance.

-- Alex Yakhnin, Device Application Developer MVP | http://blog.opennetcf.org/ayakhnin

AlexY

Probably you can inherit your own Window class from the stock Window and use it everywhere.
P.S. Have you implemented window mouse resizing functionality as well? Does it works fine?

EugeneZ

>Probably you can inherit your own Window class from the stock Window and use it everywhere.

AlexY

Alex, in v1.0 of WPF, you cannot subclass from a xaml generated class, probably this feature will be checked in in the v2.0.

Sheva

WPF C# & Other .Net Related Goodness http://shevaspace.spaces.live.com/

footballism

>I was thinking about that. Still trying to figure out how to declare XAML for the new window >that inherits from my custom window. This is what I am doing:

EugeneZ

If to take into view the thing Footbalism wrote, I would rather write the base class code in a procedural manner. In context of WPF it is quite inconvinient, but at least it probably will work.

EugeneZ

Yeah... IMO, this kinda defeats the whole XAML useability.

-- Alex Yakhnin, Device Application Developer MVP | http://blog.opennetcf.org/ayakhnin

AlexY

Well, Alex, one ulgy trick you can do here is that, you define the OfficeWindow class in the standalone assembly, and apply the following attribute:

footballism

reply 10