Get flash to fully experience Pearltrees
Posted: March 26, 2009 in .NET Framework Tags: WPF To user hyperlink in WPF application we could do something like this < TextBlock> < Hyperlink NavigateUri =” http://www.google.co.in”> ; Click here
WPF 4 now includes, in the core runtime libraries, the calendar control. This control previously existed only in the WPF Toolkit, but has been promoted in the latest WPF release. Inclusion in the core runtime library makes it easier to develop with as there is no additional namespace declaration or reference required. The Calendar control is located in the System.Windows.Controls namespace in the PresentationFramework DLL. Let’s start with the key properties and then move on to a couple common tasks such as scaling and binding. Key Properties
(Blogging Tunes: Screaming Headless Torsos - "1995") We've talked about hosting Windows Forms controls in WPF applications, but what about the other way? You may very well want to just keep your existing Windows Forms application and "sprinkle" in some WPF sweetness in strategic places. That means you will need some means to be able to place WPF controls side-by-side with Windows Forms controls.
Thanks to the work of the WPF Toolkit team (and especially Patrick Danino ), the February 2010 release of the WPF Toolkit includes as new components AutoCompleteBox , plus Accordion and Rating as well. Resources All of my AutoCompleteBox-related blog posts Posts about this release: David Anson’s , Patrick Danino’s
Charting in WPF
Writing a custom wizard control (or simply a control of any kind) in many widely used GUI toolkits is usually a challenging task. But it turns out that doing such a control in WPF is rather easy. In this post, I'm going to explain how to create stylable, simple wizard that looks like this: I recommend briefly examining attached source code before reading the post because the code is not short enough to be pasted on a blog.
In my previous post about rolling your own WPF wizard control, I've described how one can easily create simple, styleable wizard in WPF. Generally, I blogged that the wizard consists of two things, namely Wizard class - representing the wizard with its buttons (Next, Previous, Finish, etc.) and simple behavior concerned around managing which wizard page should be displayed, WizardPage class - representing a container for a single wizard page. The first class inherited from the Control class whereas the second inherited from the ContentControl class. Because the Wizard class wasn't derived from any control that can have content, it had to have a bindable collection of wizard's pages.