Browse by Tags

• .NET 3.0
• .net 3.5
• Avalon
• Programming
• Windows Presentation Foundation
• WPF

• 3.5 features: Addins

  In 3.0, we received a number of queries regarding creating plugins. So in 3.5 we got this in .. :) .. Creating an adding would bsically need the use of 3 dlls - System.Addin, System.Addin.Contract, System.Presentation The basic steps to create the addins involves creating a contract, then create the corresponding views and adapsters for both the host and the addin. So in total you will be creating 5 dlls in addition to the app and the actual addin. Even though this looks a bit overwhelming, its pretty simple. http://blogs.msdn.com/clraddins/ gives more information about creating addins. In order to try out this framework, I added the addin support to blogpad with the host being able to set text in the addins... So the app basically has an addin for a calculator (which can be removed) and an ad at the side... You can try out the code that is attached .. FYI, the ad plugin links to an xbap and this line is commented in code.. You might want to point it to a legit xbap to get this plugin working. Read More... Posted Thursday, August 16, 2007 11:34 AM from Lester's WPF blog | 0 Comments Filed under: WPF, Programming, .NET 3.0, WPF samples, Vista, Windows Presentation Foundation, .net 3.5

• WPF Blog Writer

  Recently, I was trying my hand at creating a simple blog writer. The writer came out pretty nice. The app makes use of a base richEditor control (thanks to Praj ).. After a bit of tweaking it ended up like the above... So the app just makes a simple call in the xaml <custom:RichEditor/> ...tada ... you have it there!!! The next thing is to write to a blog... In this case, the writer is coded to post the entry on blogger, which makes use of the Google data API .. this could easily be changed for other blogs. It also makes use of a Xaml-HTML converter as the string passed needs to be in HTML. For now, its a blog writer - hence, it onluy writes. But it could easily be extended into a full blown Blog client. Do I hear anyone taking it up :) The code is attached .. so have fun with it .. Share this post Read More... Posted Tuesday, June 05, 2007 3:47 PM from Lester's WPF blog | 0 Comments Filed under: WPF, Avalon, Programming, .NET 3.0, WPF samples, Vista, Windows Presentation Foundation

• Vista style Open/Save FileDialogs

  If you have tried creating FileDialogs in WPF, they usually do not blend well into the Vista look. The solution is to use the wrappers provided in the VistaBridge library which is part of the SDK samples. You could include the library dll (around 100k) in your project and then make the simple call to CommonOpenFileDialog/CommonSaveFileDialog ... The other option being to just include the specific classes in the project. CommonSaveFileDialog saveDialog = new CommonSaveFileDialog (); Its that easy!! Share this post Read More... Posted Monday, May 14, 2007 1:49 PM from Lester's WPF blog | 0 Comments Filed under: WPF, Avalon, Programming, .NET 3.0, WPF samples, Vista, Windows Presentation Foundation

• BitmapSource-Bitmap interop

  Recently I was trying my hand at a rough image editing scenario and one of the things was changing into gray scale, brightness and so forth. If you have played with .NET 2.0 you get quite a few functions which help in these types of operations and it would be nice shifting Images to Bitmaps and vice versa. As luck would have it, Robert had posted some code on this in the forums. To get the Bitmap you would have to call CopyPixels on the BitmapSource and convert it to a Bitmap- transformedBitmapSource.CopyPixels(bits, stride, 0); unsafe { fixed ( byte * pBits = bits) { IntPtr ptr = new IntPtr (pBits); System.Drawing. Bitmap bitmap = new System.Drawing. Bitmap ( width,height,stride, System.Drawing.Imaging. PixelFormat .Format32bppPArgb,ptr); return bitmap; } } To do the reverse: System.Windows.Media.Imaging. BitmapSource bitmapSource = System.Windows.Interop. Imaging .CreateBitmapSourceFromHBitmap( bitmap.GetHbitmap(), IntPtr .Zero, Int32Rect .Empty, System.Windows.Media.Imaging. BitmapSizeOptions Read More... Posted Thursday, March 08, 2007 11:50 AM from Lester's WPF blog | 0 Comments Filed under: WPF, Avalon, Programming, .NET 3.0, WPF samples, Vista, Windows Presentation Foundation

• Listening to DependencyProperty changes

  Dependency property is a pretty kewl concept. You got to agree on that J . One the nice features is the ability to listen to the changes in these properties and I tend to use it a lot. The SDK way would be to derive from the control, override the dependencyproperty metadata and specify the propertychangedCallback in the signature. Hmmm… pretty cumbersome you would say. public class MyTextBox : TextBox { public MyTextBox(): base () { } static MyTextBox() { FlowDirectionProperty.OverrideMetadata( typeof ( MyTextBox ), new FrameworkPropertyMetadata ( new PropertyChangedCallback (FlowDirectionPropertyChanged))); } private static void FlowDirectionPropertyChanged( DependencyObject sender, DependencyPropertyChangedEventArgs args) { (( MyTextBox )sender).FontWeight = ((( MyTextBox )sender).FlowDirection == FlowDirection .RightToLeft) ? FontWeights .Bold : FontWeights .Normal; } } But hey, things get easy, thanks to Ben . What you can do is use the DependencyPropertyDescriptor. DependencyPropertyDescriptor Read More... Posted Monday, March 05, 2007 11:30 AM from Lester's WPF blog | 0 Comments Filed under: WPF, Avalon, Programming, .NET 3.0, WPF samples, Vista, Windows Presentation Foundation

• Determining the Visibility of Elements inside Scrollviewer

  A ScrollViewer is a very handy control. One of the problems, however, is bringing a control to Focus or scrolling to the item. If this is done manually, that’s not an issue. But programmatically hmm.. You can hit some issues. The simplest way is to call the scrollviewer’s ScrollToVerticalOffset() with the offset being the Y co-ordinate. But what if the element is partially visible and you do not want it to scroll. This would require determining if the element is in the ScrollViewers viewport. The way to achieve this is simple. Suppose ContainedObject is the element inside the Scrollviewer (ScrollViewerObj) // position of your visual inside the scrollviewer GeneralTransform childTransform = ContainedObject .TransformToAncestor( ScrollViewerObj ); Rect rectangle = childTransform.TransformBounds( new Point (0,0), ContainedObject .RenderSize); //Check if the elements Rect intersects with that of the scrollviewer's Rect result = Rect .Intersect( new Rect ( new Point (0, 0), ScrollViewerObj .RenderSize),rectangle); Read More... Posted Thursday, January 18, 2007 1:06 PM from Lester's WPF blog | 0 Comments Filed under: WPF, Avalon, Programming, .NET 3.0, WPF samples, Vista, Windows Presentation Foundation