Volunteer .NET Evangelist

A well oiled machine can’t run efficiently, if you grease it with water.
   :: 首页 ::  :: 联系 :: 订阅 订阅 :: 管理

2006年10月3日

Two Xaml Tricks

1. Declare array object in xaml:

<Page xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
            xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
            xmlns:sys="clr-namespace:System;assembly=mscorlib">

    <Grid>
        <ListBox Width="200" Height="200" BorderBrush="Navy" BorderThickness="1">
            <ListBox.ItemsSource>
                <x:Array Type="{x:Type sys:String}">
                    <sys:String>Paviel Dedved</sys:String>
                    <sys:String>Andriy Shevchenko</sys:String>
                    <sys:String>Paolo Maldini</sys:String>
                    <sys:String>Robert Baggio</sys:String>
                    <sys:String>Alessandro Del Piero</sys:String>
                </x:Array>
            </ListBox.ItemsSource>
        </ListBox>
    </Grid>
</Page>

2. Declare inline code in Xaml:

<Page xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" 
           xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" 
           x:Class="MyPage">
  <x:Code>
    <![CDATA[
      private void ButtonClickEventHandler(Object sender, RoutedEventArgs e)
      {
          MessageBox.Show("Hello Xaml!");
      }
    ]]>
  </x:Code>
  <Grid>
    <Button Width="200" Height="60" Content="Click Me" Click="ButtonClickEventHandler"/>
  </Grid>
</Page>

    Note that, when specifying inline code in xaml, you also need to specify the x:Class and the Xaml should be compiled before getting execution, which means that XamlReader.Load() method cannot intepret the xaml which contains inline code.

posted @ 2006-10-03 15:18 Sheva 阅读(1534) 评论(2) 编辑

2006年9月26日

I See Cool Stuff Today

    Just paste the following xaml into the XamlPad shipped with Microsoft Windows SDK or the XamlPad I create myself, you will get some unexpected surprise, really cool indeed:

<Viewbox xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
         xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
         Margin="10"
         OpacityMask="#99000000">
    <Button/>
</Viewbox>

    This is what I get in my own XamlPad:



posted @ 2006-09-26 20:54 Sheva 阅读(734) 评论(1) 编辑

2006年9月23日

DataTemplate Is A Bit Naughtier To Play With

摘要: Some one pointed out on MSDN WPF forum post that FindName breaks on DataTemplate, when we want to reference the visual elements inside the data template, we cannot use FindName, then what we can use? ...阅读全文

posted @ 2006-09-23 23:05 Sheva 阅读(2763) 评论(2) 编辑

2006年8月28日

XmlnsDefinitionAttribute Is Pretty Nifty

    When we want to declaratively use our custom controls or reference the types we defined in XAML, we should declare the XML namespace to map to the CLR namespace in which the controls and types are defined as the following XAML snippt demonstrates:

<Page x:Class="Test.MainWindow"
         xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" 
         xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
         xmlns:cc="clr-namespace:Sheva.Windows.Controls;assembly=AvalonLib"
/>

    Recently, I am heavily engaged with writing a resuable WPF control library, and quite often I need to create some pages to test those controls I create, so ever now and then I have to use the cumbersome syntax like above to declare the XML namespace, personally I don't like the syntax, and I thought Microsoft WPF team should come up with a more elegant way of doing it, and in actuality, they did introduce an alternative to do it since the CTP releases. there is a custom attribute called XmlnsDefinitionAttribute in the System.Windows.Markup namespace which allows you to apply to the assembly which contains the types and controls the XAML code would reference.the built-in WPF assemblies such as WindowsBase.dll, PresentationCore.dll, and PresentationFramework.dll all have this attribute applied, and all have http://schemas.microsoft.com/winfx/2006/xaml/presentation namespace mapped with the CLR namespaces introduced by them. and of cause you can use this attribute in your own project, just open the AssemblyInfo.cs file, and append the following directive:

[assembly: XmlnsDefinition("http://schemas.sheva.com/wpf/", "Sheva.Windows.Controls")]

    Then you can declare the namespace alias in XAML this way:

<Page x:Class="Test.MainWindow"
         xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" 
         xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
         xmlns:cc="http://schemas.sheva.com/wpf/"
/>
   
    Wow, this is a bit like the built-in xmlns declaration indeed, really really cool indeed:)

posted @ 2006-08-28 23:37 Sheva 阅读(2650) 评论(0) 编辑

2006年8月24日

Application.DoEvents In WPF

    Recently, I am tied up writing a custom WPF control called FolderPicker, and I come to the scenario that when I update the data source, I want to let the UI thread to update the control UI, basically, at this time, I should force the dispatcher to process the layout message, in Windows Forms application, If we want to process the windows message such as WM_SIZE, WM_PAINT messages in an event handler, we can call the Application.DoEvents(), then how about in WPF?
    Actually, WPF doesn't provide such an API, the reason is a bit complicated, and really worth a new post contributing to it, then how to implement such kinda API in WPF, after some examination on this problem, and thanks to Kevin Moore's WPF samples code and Ian Griffiths helpful tips, I finally come up with my own implementation of Application.DoEvents logic.
  

using System;

using System.Windows;

using System.Windows.Threading;

 

namespace Sheva.Windows

{

    /// <summary>

    /// Designates a Windows Presentation Foundation application model with added functionalities.

    /// </summary>

    public class WpfApplication : Application

    {

        private static DispatcherOperationCallback exitFrameCallback = new

                                DispatcherOperationCallback(ExitFrame);

 

        /// <summary>

        /// Processes all UI messages currently in the message queue.

        /// </summary>

        public static void DoEvents()

        {

            // Create new nested message pump.

            DispatcherFrame nestedFrame = new DispatcherFrame();

 

            // Dispatch a callback to the current message queue, when getting called,

            // this callback will end the nested message loop.

            // note that the priority of this callback should be lower than the that of UI event messages.

            DispatcherOperation exitOperation = Dispatcher.CurrentDispatcher.BeginInvoke(

                                                  DispatcherPriority.Background, exitFrameCallback, nestedFrame);

 

            // pump the nested message loop, the nested message loop will

            // immediately process the messages left inside the message queue.

            Dispatcher.PushFrame(nestedFrame);

 

            // If the "exitFrame" callback doesn't get finished, Abort it.

            if (exitOperation.Status != DispatcherOperationStatus.Completed)

            {

                exitOperation.Abort();

            }

        }

 

        private static Object ExitFrame(Object state)

        {

            DispatcherFrame frame = state as DispatcherFrame;

 

            // Exit the nested message loop.

            frame.Continue = false;

            return null;

        }

    }

}


    The theory behind the code shown above is that when pushing a nested message loop, the nested message loop will immediately process the messages in the queue, so the layout or other window messages can get processed. But you should avoid using nested message loop if at all possible, because as Ian Griffths says:"bad things happen when you nest message pumps." what does this mean? let me save it for another day:)
    Edit: Jessica Fosler has wrriten an awesome article on Application.DoEvents which is really worth a read.

posted @ 2006-08-24 23:56 Sheva 阅读(15988) 评论(2) 编辑

2006年8月17日

征召译者

摘要: 现电子工业出版社急招四名翻译人员来翻译Charles Petzold刚刚出炉的新书《Applications = Code + Markup》，要求译者熟悉Windows桌面程序的开发，熟悉.NET编程，对WPF有一定的了解，并具有很强的英语翻译能力。稿费，翻译内容分工等具体事宜容日后再议，请有意者速与我或是梁晶联系。联系人：梁晶(Dinla) (电子工业出版社编辑) email: fordin ...阅读全文

posted @ 2006-08-17 20:25 Sheva 阅读(2859) 评论(22) 编辑

2006年5月6日

C# Trivia Test

摘要: Eric Gunnerson just brings up a series of posts on some C# trivia that probably most developers don't know about, I just quote some of them which are more relevant to the C# technicality:Language Deta...阅读全文

posted @ 2006-05-06 20:28 Sheva 阅读(904) 评论(0) 编辑

2006年4月29日

CreateParams Is Pretty Cool!

摘要: Probably I've been in the WPF world for so long that I need to try something different, yesterday, I come across a Channel9 forum thread on how to use windows forms' Control.CreateParams property, whi...阅读全文

posted @ 2006-04-29 23:30 Sheva 阅读(1990) 评论(7) 编辑

2006年4月27日

In-Place Editing In WPF

摘要: Several days ago, Dflying Chen just shown us how to implement in-place editing functionality using ASP.NET Atlas framework, and the custom control he writes called InPlaceEditingInput is pretty cool i...阅读全文

posted @ 2006-04-27 23:03 Sheva 阅读(2848) 评论(6) 编辑

2006年4月23日

SingleLinkedList Implementation

摘要: ILinkedList interface definitionCode highlighting produced by Actipro CodeHighlighter (freeware)http://www.CodeHighlighter.com/-->usingSystem;usingSystem.Collections.Generic;namespaceSheva.Collections...阅读全文

posted @ 2006-04-23 23:43 Sheva 阅读(594) 评论(0) 编辑

仅列出标题  下一页