Till now are are applying template only at the list view header. This time we are going to apply template in the list view item. In this example we are going to insert the expender control inside the cell of the grid view. We are using data template for this purpose. We are going to apply on GridViewColumn and use its CellTemplate property. CellTemplate is a DataTemplate type property. Here is a piece of code to insert expender inside the list view.

  1: <GridViewColumn.CellTemplate>

  2: 	<DataTemplate>

  3: 		<Expander ExpandDirection="Right">

  4: 			<TextBlock Foreground="Green" FontSize="14" Text="{Binding NickName}"/>

  5: 		</Expander>

  6: 	</DataTemplate>

  7: </GridViewColumn.CellTemplate>

  8: 

Rest of the code is almost same as we saw earlier. Here is a complete XAML code of the project.

  1: <Window x:Class="UIElement.Window1"

  2:     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

  3:     xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

  4:     xmlns:local="clr-namespace:UIElement"

  5:     Title="ListView Example" Height="300" Width="400">

  6:     <Window.Resources>

  7:         <Style x:Key="myStyle" TargetType="{x:Type ListViewItem}">

  8:             <Setter Property="Background" Value="AliceBlue"/>

  9:             <Setter Property="FontSize" Value="14"/>

 10:             <Setter Property="Foreground" Value="Green"/>

 11:         </Style>

 12:     </Window.Resources>

 13:     <Grid>

 14:         <ListView ItemContainerStyle="{StaticResource myStyle}" Name="list" Margin="5" HorizontalContentAlignment="Stretch">

 15:             <ListView.View>

 16:                 <GridView>

 17:                     <GridView.ColumnHeaderTemplate>

 18:                         <DataTemplate>

 19:                             <Border BorderBrush="Brown" BorderThickness="2" CornerRadius="5">

 20:                                 <Border.Background>

 21:                                     <LinearGradientBrush>

 22:                                         <GradientStop Offset="0" Color="Wheat"/>

 23:                                         <GradientStop Offset="1" Color="LightCoral"/>

 24:                                     </LinearGradientBrush>

 25:                                 </Border.Background>

 26:                                 <TextBlock Foreground="Blue" FontSize="14" FontWeight="Bold" Margin="5" Text="{Binding}" Width="Auto"/>

 27:                             </Border>

 28:                         </DataTemplate>

 29:                     </GridView.ColumnHeaderTemplate>

 30:

 31:                     <GridViewColumn Width="Auto" Header="State Name" DisplayMemberBinding="{Binding Path=Name}"/>

 32:                     <GridViewColumn Width="Auto" Header="State Capital" DisplayMemberBinding="{Binding Path=Capital}"/>

 33:                     <GridViewColumn Width="Auto" Header="State Nick Name">

 34:                         <GridViewColumn.CellTemplate>

 35:                             <DataTemplate>

 36:                                 <Expander ExpandDirection="Right">

 37:                                     <TextBlock Foreground="Green" FontSize="14" Text="{Binding NickName}"/>

 38:                                 </Expander>

 39:                             </DataTemplate>

 40:                         </GridViewColumn.CellTemplate>

 41:                     </GridViewColumn>

 42:                 </GridView>

 43:             </ListView.View>

 44:         </ListView>

 45:     </Grid>

 46: </Window>

 47: 

C# code of this project is also same as previous project. Here is complete C# code of this project.

  1: using System;

  2: using System.Collections.Generic;

  3: using System.Linq;

  4: using System.Text;

  5: using System.Windows;

  6: using System.Windows.Controls;

  7: using System.Windows.Data;

  8: using System.Windows.Documents;

  9: using System.Windows.Input;

 10: using System.Windows.Media;

 11: using System.Windows.Media.Imaging;

 12: using System.Windows.Navigation;

 13: using System.Windows.Shapes;

 14:

 15: namespace UIElement

 16: {

 17:     /// <summary>

 18:     /// Interaction logic for Window1.xaml

 19:     /// </summary>

 20:     public partial class Window1 : Window

 21:     {

 22:         public Window1()

 23:         {

 24:             InitializeComponent();

 25:

 26:             List<StateInfo> statesList = new List<StateInfo>();

 27:

 28:             statesList.Add(new StateInfo("Maryland", "Annapolis", "Old Line State", "Eastern"));

 29:             statesList.Add(new StateInfo("California", "Sacramento", "Golden State", "Pacific"));

 30:             statesList.Add(new StateInfo("Washington", "Olympia", "Ever Green State", "Pacific"));

 31:             statesList.Add(new StateInfo("Taxes", "Austin", "Lone Star State", "Central"));

 32:             statesList.Add(new StateInfo("New York", "Albany", "Empire State", "Eastern"));

 33:

 34:             list.ItemsSource = statesList;

 35:         }

 36:     }

 37:

 38:     public class StateInfo

 39:     {

 40:         public StateInfo()

 41:         {

 42:         }

 43:

 44:         public StateInfo(String name, String capital, String nickName, String timeZone)

 45:         {

 46:             Name = name;

 47:             Capital = capital;

 48:             NickName = nickName;

 49:             TimeZone = timeZone;

 50:         }

 51:

 52:         public String Name

 53:         { get; set; }

 54:

 55:         public String Capital

 56:         { get; set; }

 57:

 58:         public String NickName

 59:         { get; set; }

 60:

 61:         public String TimeZone

 62:         { get; set; }

 63:     }

 64: }

 65: 

Here is the output of this program.

With the help of horizontal expender, now we can make the state nick name demand base, means user can see the nick name of his/her selected states.

Or what you are going to call it, an unrealized proposal from Aerojet around 1984. PDF Found on NTRS.

The idea was to have two turbopumps (like on SSME), but instead operate on the expander cycle. Two heat exchangers, two turbines, two pumps. One for each propellant.

Both propellants go through a heat exchanger and an expander driving a pump

This is a LOX-hydrogen engine. Also this means that since there is the same propellant on both sides of the axle, in the turbine and in the pump, no elaborate seals are needed. Original intent for these engines was for in-space reusable stuff, that needs to be operated many times and for a long time without maintenance. Size was in the RL10 class, about 70 kN. (RL10 has grown though.)

Think for example if you let a fired turbopump sit in space for a long time. Will some fuel leak to the oxidizer side through the seals? This could avoid that. (You can use helium purges too though but then you’ve got one more fluids you need to tank.)

I have recently shared this code with a few people and its something I use myself so I thought I would share it publicly.

I was having a problem that when the Expander was collapsed the grid containing the expander did not resize properly unless it was recycled. In my case this grid was inside a DataGrid. So those this code is specific to my use (of an expander inside a grid) it can be easily adapted to other types of containers…or you can just wrap your expander in a grid and use it like its posted!

Just add this to your Expander_Collapsed event and call it good.

The sheer number of panel layout combinations can be overwhelming to WPF newcomers, I know it was for me! Having been used to traditional Windows Forms and fairly simple UI panel layouts, WPF really removes all the restrictions on what can be done, but takes a little getting used to.

While experimenting with simple layouts I came across a nice way to use a ScrollViewer control inside of an Expander. This is typical of my experiences of WPF thus far, in that the WPF layout is so flexible in what you can do some things are not immediately obvious until you start playing around with different combinations. In this case it was when I had three expanders inside a parent expander, as show below.

Now, if users behave themselves and don’t resize the main Window then every thing is fine. But if you decrease the height of the Window then, when all three child Expander controls are expanded, some controls will disappear of the screen!

Hmm, not really desirable. So, a nice remedy that will keep users happy is wrap the child Expander controls inside of a ScrollViewer control. When the user resizes the Window that would normally obscure other controls, the Window displays a scroll bar so the missing controls can be bought back into view again. All the code for thr three child Expanders is wrapped inside a StackPanel control, so all we need to do is to place this code inside a ScrollViewer container. The full code for the parent Expander is shown below.

<ScrollViewer VerticalScrollBarVisibility="Auto">
   <StackPanel Width="230">
      <Border Margin="10" Background="#FFE6E6E6" CornerRadius="8" Padding="5" BorderBrush="#FF4F4F4F" BorderThickness="1">
         <TextBlock Text="Expand/collapse the sections below to view available options." TextWrapping="Wrap" Height="31.92"/>
      </Border>
      <Expander x:Name="expander1" Margin="8,8,0,0" RenderTransformOrigin="0.5,0.5">
         <Expander.Header>
    	   <TextBlock FontSize="13.333" FontStyle="Italic" Foreground="#FFEA3939"><Run FontSize="14.667" Text="Expander #1"/></TextBlock>
    	 </Expander.Header>
    	 <Border Width="190" BorderThickness="0,0,0,0.5" BorderBrush="#FF949494">
    	    <StackPanel Height="85.718">
    	       <Button Content="Button" Margin="22.286,10,26.999,10" Height="22.859" HorizontalContentAlignment="Center" VerticalContentAlignment="Top"/>
               <Button Content="Button" Margin="22.286,10,26.999,10" Height="22.859" HorizontalContentAlignment="Center" VerticalContentAlignment="Top"/>
            </StackPanel>
         </Border>
      </Expander>
      <Expander x:Name="expander2" Margin="8,8,0,0" Background="Transparent" RenderTransformOrigin="0.5,0.5">
         <Expander.Header>
    	    <TextBlock Text="Expander #2" Foreground="#FF55C724" FontStyle="Italic" FontSize="14.667"/>
    	 </Expander.Header>
    	 <StackPanel HorizontalAlignment="Left" VerticalAlignment="Top" Width="100">
    	    <Button Content="Button" Margin="22.286,10,26.999,10" Height="22.859" HorizontalContentAlignment="Center" VerticalContentAlignment="Top"/>
    	    <Button Content="Button" Margin="22.286,10,26.999,10" Height="22.859" HorizontalContentAlignment="Center" VerticalContentAlignment="Top"/>
    	 </StackPanel>
      </Expander>
      <Expander x:Name="expander3" Margin="8,8,0,0" Background="Transparent" RenderTransformOrigin="0.5,0.5">
         <Expander.Header>
    	    <TextBlock Text="Expander #3" Foreground="#FF2A4BE0" FontStyle="Italic" FontSize="14.667"/>
    	 </Expander.Header>
    	 <StackPanel HorizontalAlignment="Left" VerticalAlignment="Top" Width="100">
    	    <Button Content="Button" Margin="22.286,10,26.999,10" Height="22.859" HorizontalContentAlignment="Center" VerticalContentAlignment="Top"/>
    	    <Button Content="Button" Margin="22.286,10,26.999,10" Height="22.859" HorizontalContentAlignment="Center" VerticalContentAlignment="Top"/>
         </StackPanel>
      </Expander>
   </StackPanel>
</ScrollViewer>

Now when the Window height is reduced, a scroll bar automatically appears to allow the parent Expanders content to be viewed by dragging the scroll bar up and down.

The ScrollViewer attribute VerticalScrollBarVisibility="Auto" describes how the vertical scroll bar should be rendered. If set to just “visible” then the scroll bar will always be visible even when it isn’t needed (in which case it appears, but is disabled). Setting it to “Auto” means that it is only displayed when required, as shown above.

I recently noticed one post in WPF form about how to make every element of list box expendable. We already have one control expender to do exactly the same thing now the only thing we have to do it make every element of list box expender.

There was already one solution there. That solution was using the control template. Here i am going to do the same thing with data template.

Both techniques has some advantages and disadvantages. If we have lots of list box control in our program and we want to make every control behave like this then control template is a good idea. On the other hand if we want to make different list box display data differently then we can do it easily with data template. Such as we want to display expander in one list box, but stack in another one and nothing at all in third list box then we can define the data template of each list box.

Let’s take a look at our old example of display state information in a list box. Now we are going to display the state name with expender control and when user press the expender then we will show rest of the information. Here is our simple XAML file to make list box with data template.

  1: <Window x:Class="WpfListBox2.Window1"

  2:     xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

  3:     xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

  4:     Title="ListBox Expender" Height="400" Width="400" Loaded="Window_Loaded">

  5:     <Grid>

  6:         <ListBox Name="lst" Margin="5" ItemsSource="{Binding}" HorizontalContentAlignment="Stretch">

  7:             <ListBox.ItemTemplate>

  8:                 <DataTemplate>

  9:                     <StackPanel>

 10:                         <TextBlock Margin="5" FontSize="16" FontWeight="Bold" Text="{Binding Path=Name}"/>

 11:                         <Expander Name="expender">

 12:                             <Border Margin="5" Background="Wheat" BorderThickness="5" BorderBrush="Brown">

 13:                                 <StackPanel>

 14:                                     <TextBlock Margin="5" FontSize="16" FontWeight="Bold" Text="{Binding Path=Name}"/>

 15:                                     <TextBlock Margin="5, 0"  Foreground="Blue" Text="{Binding Path=Capital}"/>

 16:                                     <TextBlock Margin="5, 0"  Text="{Binding Path=BigCity}"/>

 17:                                     <TextBlock Margin="5, 0" Text="{Binding Path=NickName}"/>

 18:                                 </StackPanel>

 19:                             </Border>

 20:                         </Expander>

 21:                     </StackPanel>

 22:                 </DataTemplate>

 23:

 24:             </ListBox.ItemTemplate>

 25:         </ListBox>

 26:     </Grid>

 27: </Window>

 28: 

Here is our C# code. We create our class to store information about the state and then create a list that class. At the time of loading the window we populate the list box and then assign it to the listbox.

  1: using System;

  2: using System.Collections.Generic;

  3: using System.Linq;

  4: using System.Text;

  5: using System.Windows;

  6: using System.Windows.Controls;

  7: using System.Windows.Data;

  8: using System.Windows.Documents;

  9: using System.Windows.Input;

 10: using System.Windows.Media;

 11: using System.Windows.Media.Imaging;

 12: using System.Windows.Navigation;

 13: using System.Windows.Shapes;

 14:

 15: namespace WpfListBox2

 16: {

 17:     /// <summary>

 18:     /// Interaction logic for Window1.xaml

 19:     /// </summary>

 20:     public partial class Window1 : Window

 21:     {

 22:         public Window1()

 23:         {

 24:             InitializeComponent();

 25:         }

 26:

 27:         private void Window_Loaded(object sender, RoutedEventArgs e)

 28:         {

 29:             List<StateInfo> states = new List<StateInfo>();

 30:

 31:             states.Add(new StateInfo("Maryland", "Annapolis", "Baltimore", "Old Line State"));

 32:             states.Add(new StateInfo("Washington", "Olympia", "Seattle", "The Evergreen State"));

 33:             states.Add(new StateInfo("California", "Sacramento", "Los Angeles", "Golden State"));

 34:             states.Add(new StateInfo("Taxes", "Austin", "Houston", "Lone Star State"));

 35:             states.Add(new StateInfo("New York", "Albany", "New York City", "Empire State"));

 36:

 37:             lst.ItemsSource = states;

 38:

 39:         }

 40:     }

 41:

 42:     public class StateInfo

 43:     {

 44:         public StateInfo(string name, string capital, string bigcity, string nickname)

 45:         {

 46:             Name = name;

 47:             Capital = capital;

 48:             BigCity = bigcity;

 49:             NickName = nickname;

 50:         }

 51:

 52:         public string Name

 53:         { get; set; }

 54:

 55:         public string Capital

 56:         { get; set; }

 57:

 58:         public string BigCity

 59:         { get; set; }

 60:

 61:         public string NickName

 62:         { get; set; }

 63:     }

 64:

 65: }

 66: 

Here is the output of this program.

This is the second post in this WPF learning series. In this post I will be writing about creating your own custom controls in WPF. I am going to write a custom expander which has similar features as of the WPF expander control plus it will have a feature of showing a Popup on mouse over event of this expander. Content of this popup will be the content of the expander itself. This is the kind of feature where a user wants to see the content of expander while hovering the mouse over the expander header, just like IE8 tab quick preview where it shows a preview of tab content without even opening the tab. So below are our set of requirements:

Requirements

• It should be an expandable control with a header and content property.
• It should show a popup when mouse is over the header and control is in collapsed state.
• Should have an option for showing/hiding the popup.
• Popup properties like position, size, transparency etc should be configurable.

Choosing the Proper base class

While writing a custom control one must choose the base control which he/she wants to extend with little care with having all the features in mind. For our requirements, we need a base class which provides me a header, a content property. In WPF we have some choices like HeaderedContentControl class and we have an Expander class which itself drives from HeaderedContentControl class. we can use any of them. I decided to use Expander class (well while coding I wasn’t sure what all I wanted to have ).

Implementation

Visual studio 2008 provides a project of type “WPF Custom Control Library” which can be used as a starting point for writing your first custom control. Following figure shows the selection of new project type.

When adding this project type to your visual studio solution, it will add a new project with following items to your solution structure:

1. CustomControl1.cs: This file contains your custom control class.
2. Themes Folder with Generic.xaml: This folder will contain the styles for all your custom controls. By default a new style for the customcontrol1 is added to the generic.xaml. One needs to change this style to work with this custom control.

Lets start implementing the new expander with popup. As we have decided we will be using Expander class as the base class for our control. I will be naming this control as CustomExpander.

  1: namespace CustomControls
  2: {
  3:     /// <summary>
  4:     /// This class is an extention to Expander Control. 
  5:     /// This provides a feature for shouwing a popup with the content of the expander on MouseOver
  6:     /// </summary>
  7:     public class CustomExpander : Expander
  8:     {
  9:         #region // .ctor(s)
 10:         static CustomExpander()
 11:         {
 12:             DefaultStyleKeyProperty.OverrideMetadata(typeof(CustomExpander), new FrameworkPropertyMetadata(typeof(CustomExpander)));
 13:         }
 14:         public CustomExpander()
 15:         {
 16:         }
 17:         #endregion
 18:     }
 19: }

The above class definition has a static ctor and a normal default ctor for the CustomExpander class. The static ctor is used to initialize the static properties of the class as well as changing the default style for the control. As highlighted in the above code snippet in line 12, DefaultStyleKeyProperty is used to change the default style for the control by passing the type of the new control.

Now we have to decide upon what all configurable properties we want to expose to the end user of this control. As mentioned in the requirement section above, we will have following dependency properties in our control:

1. PopUpPlacementModeProperty: This property will allow user to configure the placement of popup in the screen. This is of type PlacementMode.
2. StaysOpenProperty: This property defines whether the popup will stay open when the popup looses focus. This is of type Boolean.
3. AllowsTransparencyProperty: This property allows user to set the transparency for the popup. This is a Boolean value.
4. PopUpWidthProperty: Width of the popup. This is of type Double
5. PopUpHeightProperty: Height of the popup. This is of type Double

Now lets us decide what controls we will be using to give this control a look of an Expander. For Expander functionality I will use ToggleButton control and a ContentPresenter control. since toggle button has the notion of being in two state (clicked and non clicked), so these state we can use to denote expanded and collapsed state of the expander. For popup functionality we will use wpf PopUp control.

So here is our task, on mouse hover on the togglebutton, set content of the expander as the child of  popup. and on click of the expander show the contentpresenter .   simple enough .. hmmmmmm

But here comes the issue. As we are talking about setting the content of popup same as the content of the expander but any object/ control can be child of only one parent. So we need make sure that while we show the popup or expand the expander only one of them have their content property set and the other one has this as null. To accomplish this we need one more dependency property which will store the content of the expander and we will use this property as the child for popup as well expander but only one at a time.

  1: public static readonly DependencyProperty OldContentProperty =
  2:                    DependencyProperty.Register("OldContent", typeof(object), typeof(CustomExpander));
  3:
  4: private object OldContent
  5: {
  6:      get { return GetValue(OldContentProperty); }
  7:      set { SetValue(OldContentProperty, value); }
  8: }
  9:

Now lets create the style for Expander. First lets design the header for the Expander. So we need a circle with an arrow indicating the expand/collapse direction and a content presenter showing the text of the header. Following code shows the style for the toggle button header.

  1: <!-- Style for the toggle button which wil be used as expander header -->
  2: <Style TargetType="{x:Type ToggleButton}" x:Key="toggleButtonKey">
  3:      <Setter Property="Template">
  4:           <Setter.Value>
  5:                 <ControlTemplate TargetType="{x:Type ToggleButton}">
  6:                        <StackPanel Orientation="Horizontal"
  7:                                  Margin="{TemplateBinding Padding}">
  8:                               <Grid Background="Transparent">
  9:                                    <!-- Circles for the expander header containg the expand direction arrow -->
 10:                                    <Ellipse x:Name="circle"
 11:                                             HorizontalAlignment="Center" VerticalAlignment="Center"
 12:                                             Width="20" Height="20"
 13:                                             Stroke="DarkGray"/>
 14:                                    <Ellipse x:Name="shadow" Visibility="Hidden"
 15:                                             HorizontalAlignment="Center" VerticalAlignment="Center"
 16:                                             Width="17" Height="17" />
 17:
 18:                                    <!-- Expand direction Arrow -->
 19:                                    <Path x:Name="arrow"
 20:                                             VerticalAlignment="Center" HorizontalAlignment="Center"
 21:                                             Stroke="#666" StrokeThickness="2"
 22:                                             Data="M1,1 L4,4 7,1" />
 23:                               </Grid>
 24:
 25:                               <!-- Expander Header Content -->
 26:                               <ContentPresenter ContentSource="{TemplateBinding Content}" Grid.Column="1" Margin="5"/>
 27:                        </StackPanel>
 28:
 29:                        <ControlTemplate.Triggers>
 30:                              <!-- Trigger to change the arrow direction when expanded -->
 31:                              <Trigger Property="IsChecked" Value="true">
 32:                                     <Setter TargetName="arrow"
 33:                                             Property="Data" Value="M 1,4  L 4,1  L 7,4"/>
 34:                              </Trigger>
 35:
 36:                              <!-- Trigger to give a mouse over effect on the circle containing direction arrow -->
 37:                              <Trigger Property="IsMouseOver" Value="true">
 38:                                     <Setter TargetName="circle"
 39:                                             Property="Stroke" Value="#666"/>
 40:                                     <Setter TargetName="arrow"
 41:                                             Property="Stroke" Value="#222"/>
 42:                                     <Setter TargetName="shadow"
 43:                                             Property="Visibility" Value="Visible"/>
 44:                               </Trigger>
 45:                       </ControlTemplate.Triggers>
 46:               </ControlTemplate>
 47:         </Setter.Value>
 48:    </Setter>
 49: </Style>

Now the expander content and popup.

  1: <!-- Expander -->
  2:                             <StackPanel>
  3:                                     <!-- Expander Header -->
  4:                                     <ToggleButton x:Name="expanderHeader"
  5:                                               Style="{StaticResource toggleButtonKey}"
  6:                                               Content="{TemplateBinding Header}"
  7:                                               Padding="{TemplateBinding Padding}"
  8:                                               IsChecked="{Binding RelativeSource={RelativeSource TemplatedParent}, Path=IsExpanded,Mode=TwoWay}"/>
  9:
 10:                                     <!-- Expander Content -->
 11:                                     <ContentPresenter x:Name="expanderContent"/>
 12:                             </StackPanel>
 13:
 14:                             <!-- PopUp control which will be showing the content of expander on mouse over -->
 15:                             <Popup x:Name="contentPopUp"
 16:                                    IsOpen="False"
 17:                                    Placement="{TemplateBinding PopUpPlacementMode}"
 18:                                    AllowsTransparency = "{TemplateBinding AllowsTransparency}"
 19:                                    StaysOpen = "{TemplateBinding StaysOpen}"
 20:                                    Width="{TemplateBinding PopUpWidth}"
 21:                                    Height="{TemplateBinding PopUpHeight}">
 22:                             </Popup>

Finally the triggers which would show the popup on mouse over and set the content.

  1: <ControlTemplate.Triggers>
  2:                         <!-- Trigger for showing the popup when Expander control is not expanded and IsMouseOver is true  -->
  3:                         <MultiTrigger>
  4:                             <MultiTrigger.Conditions>
  5:                                 <Condition SourceName="expanderHeader" Property="IsMouseOver" Value="True"></Condition>
  6:                                 <Condition SourceName="expanderHeader" Property="IsChecked" Value="False"></Condition>
  7:                             </MultiTrigger.Conditions>
  8:                             <Setter TargetName="expanderContent"
  9:                                     Property="Content" Value="{x:Null}"></Setter>
 10:                             <Setter TargetName="contentPopUp"
 11:                                     Property="Child" Value="{Binding RelativeSource={RelativeSource TemplatedParent}, Path=OldContent,Mode=OneWay,Converter={StaticResource localConverter}}"></Setter>
 12:                             <Setter TargetName="contentPopUp"
 13:                                     Property="BitmapEffect" Value="{StaticResource outerGlow}"></Setter>
 14:                             <Setter TargetName="contentPopUp"
 15:                                     Property="IsOpen" Value="True"></Setter>
 16:                         </MultiTrigger>
 17:
 18:                         <!-- Trigger for clearing the content of PopUp control when mouse is not over the expander control -->
 19:                         <Trigger SourceName="expanderHeader" Property="IsMouseOver" Value="False">
 20:                             <Setter TargetName="contentPopUp"
 21:                                     Property="Child" Value="{x:Null}"></Setter>
 22:                         </Trigger>
 23:
 24:                         <!-- Trigger for setting the content of expander when IsExpanded is true -->
 25:                         <Trigger SourceName="expanderHeader" Property="IsChecked" Value="True">
 26:                             <Setter TargetName="contentPopUp"
 27:                                     Property="Child" Value="{x:Null}"></Setter>
 28:                             <Setter TargetName="expanderContent"
 29:                                     Property="Content" Value="{Binding RelativeSource={RelativeSource TemplatedParent}, Path=OldContent,Mode=OneWay}"></Setter>
 30:                         </Trigger>
 31:                     </ControlTemplate.Triggers>

So this makes our code complete. But now as we have an option to configure the width and height of the popup. So the behavior of the popup should be something like this, It should zoom in / zoom out it self depending on the size of the content and the dimensions declared by the control user. Here comes the ViewBox wpf control. This control is made to do this. It adjusts its content according to the width/height of the viewbox. So what I will do is, I will make the content of expander as the content of a viewbox and will store this viewbox as the value of OldContent property. This will be done when the template is being applied to the control in OnApplyTemplate method. So I will override this method in our control class and store the content value.

  1: public override void OnApplyTemplate()
  2:         {
  3:             base.OnApplyTemplate();
  4:             object tmpContent = this.Content;
  5:             this.Content = null;
  6:
  7:             Viewbox containerViewBox = new Viewbox();
  8:             containerViewBox.Child = (UIElement)tmpContent;
  9:             OldContent = containerViewBox;
 10:         }

Complete source code is available here.

[PS: Please change the extension of file from .DOC to .ZIP]

Ha-P Coding

Sport bei Schnee und Eis.

Besonders Sportmuffel nutzen das kalte Winterwetter als dankbare Ausrede, um sich vor dem Sport zu drücken. Doch auch im Winter sind vielfältige Möglichkeiten geboten, sich ohne zu frieren mit ein bisschen Sport fit zu halten – wie der Onlineshop das sportlet beweist. Ob Fitnessgeräte, Sportbekleidung oder Zubehör für verschiedene Hallensportarten, hier wird jeder fündig.

Fitnessgeräte – das Studio zu Hause

Wer keine Lust auf ein Fitnessstudio hat, der ist mit den Fitnessgeräten und Crosstrainern des Onlineshops gut beraten. Die hochwertigen Kettler Ergometer, Energetics Heimtrainer und Horizon Crosstrainer sind für das Trainieren zu Hause ideal. Klein anfangen kann man mit Physioball, Hebegürtel, Hantel, Springseil und Co. Damit verschwindet auch der letzte Rest vom Winterspeck, der sich über Weihnachten und Silvester angesammelt hat. Und das Beste: Die Fitnessgeräte und Crosstrainer können ganz bequem geleast werden.

Sportbekleidung – alles sitzt

Die schönste Sportart kann durch schlecht sitzende Sportkleidung vermiest werden, wenn ständig etwas kratzt oder rutscht. Der Onlineshop das sportlet bietet deshalb eine große Auswahl an hochwertiger Sportbekleidung an. Ob Fleecepullover von Jack Wolfskin, eine Jacke von McKinley, eine Pro Touch Präsentationshose oder ein Nakamura Radtrikot – die namhaften Hersteller sorgen für eine angenehme Qualität und optimale Verarbeitung. Praktisch verpackt wird die Kleidung in den Pro Touch Sporttaschen.

Sportschuhe – die halten was aus

Um Sportunfälle und Haltungsschäden zu vermeiden, sollte man bei der Auswahl der richtigen Sportschuhe ganz besondere Sorgfalt walten lassen. Ob Adidas Fußballschuhe oder McKinley Schuhpflege und Schnürsenkel, der Onlineshop das sportlet bietet nur die beste Qualität.

Boxen, Handball und Co. – Sportarten für drinnen

Wem es im Winter für Sport draußen zu kalt ist, der findet in der großen Auswahl an Hallensportarten bestimmt seinen Favoriten. Zum Beispiel wird im Onlineshop das sportlet neben einem großen Sortiment an Sandsäcken auch Box-Zubehör, wie der Karl Schmidt Zahnschutz, der Energetics Kopfschutz oder das Pro Touch Boxsack Decken-Drehgelenk angeboten.
Handballer dürfen sich über die hohe Qualität der Trace Knieschützer freuen. Fans von Tischtennis dagegen haben die Wahl zwischen Tecno Pro Turniergarnituren, Schlägern, Reinigungsutensilien und vielem mehr.

Wintersport – da ist was los

Die weißen Schneemassen laden zum Skifahren ein. Zum Glück gibt es im Onlineshop das sportlet für jeden die richtigen Skier. Ob Tecno Pro Skier und Fischer Schuppenskier für den Langlauf oder Völklskier für die Abfahrt, hier wird jeder fündig. Tigershark und Racetiger, die Namen der Völklskier sind Programm, denn mit diesen Skiern setzt man auf Geschwindigkeit.

Wassersport – für den Sommer üben

Mit der richtigen Ausrüstung kommt selbst in den Hallenbädern eine Sommer-Urlaubs-Stimmung auf. Mit Pro Touch Badesandale, Beco Schwimmhilfe oder Tecno Pro Tauchmaske ist man für das kühle Nass perfekt ausgerüstet.

Bei diesen zahlreichen Angeboten lohnt es sich wirklich, einmal unter www.das-sportlet.de nach dem perfekten Sportartikel zu suchen, den inneren Schweinehund zu bekämpfen und sich bei seiner neuen Lieblingssportart so richtig auszupowern.

Características : 9/10

Expander dedicado a las sonoridades de órganos litúrgicos.

Lleva entrada y salida y thru MIDI, auxiliar L/R, salidas jack mono y estéreo.

Posibilidad de extensión para tarjetas SRX de Roland.

Implantación GM2.

Acabados finos con partes laterales de madera natural.

Utilización : 7/10

El manual de usuario es más o menos claro, una pantalla LCD un poco más grande fuese mejor para visualizar mensajes de manera más eficaz. La manipulación de las varias funciones no es siempre intuitiva, es un poco justo… La pantalla no muestra más de 3 dígitos.

En resumen, es un poco complicado controlarlo al principio, tampoco es muy fácil de recordar la edición de los diversos menús.

Sonoridades : 9/10

Los sonidos se dividen en dos familias : sonidos de órgano y otros sonidos.

Los sonidos dedicados a los órganos litúrgicos (flue/reed/mix/pedalera…) parecen bastante realistas, suenan bien, con sonoridades quedas y lindas definiciones.

Los otros sonidos (pianos acústicos y eléctricos, órganos eléctricos, cuerdas, percusiones, metales…) también son bien logrados, los sonidos de orquesta permiten realizar ambientes tipo películas, todo en alta definición, con varios parámetros de edición (reverb, ecualización, pitch…) que dan aún más dimensión a las sonoridades.

Opinión Global : 9/10

Advertencia : este expander se maneja normalmente con un órgano Rodgers, pero se puede manejar como cualquier otro expander. Sin embargo tiene funciones especiales que sólo son compatibles con los mensajes MIDI de un Rodgers.

En realidad existe poca información acerca de este expander y las pocas info no tratan este tema claramente.

La publicidad gallardea algunos 1000 sonidos pero en realidad embarca menos de 300, los otros vienen del modo GM2 y otros mensajes MSB/LSB que no puede manejar cualquier teclado.

Por eso lo quiero especificar, cuando he comprado este expander sin saberlo. Globalmente no me ha decepcionado aunque esté bastante caro. Por cierto incluye sonidos pocos comunes y simpáticos, pero afortunadamente permite añadir tarjetas de sonidos SRX, lo que amortigua un poco la inversión. La mayoría de los sonidos litúrgicos son bastante originales y difíciles de encontrar en otros materiales que generan sonidos, o teclados. Rodgers es una referencia en la gama de órganos litúrgicos numéricos presente en iglesias ; este expander está distribuido por Roland pero tiene la firma de Rodgers que es una filial de Roland.

Traducido de la opinión de Adrimed en AudioFanzine en Francés

http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=4103&lid=

If you’re using a Wireless-G Range Expander – WRE54G v2 or v3, you can do the following:

1. Connect the PC to LAN Port of the Range Expander
2. Assign a Static IP Address on your Wired Computer (beyond scope of this post; see link at beginning of post)

Go to http://192.168.1.240

Trzech Tenorów to nowy PP EXPANDER w Afilo.pl Jest to ferta inwestycyjna oparta o stopy zwrotu generowane przez najbardziej znanych inwestorów na świecie. Obserwując ostatnie zmiany na rynkach kapitałowych ciężko przewidzieć, jaka klasa aktywów będzie trafną inwestycją. Dzięki LOKACIE TRZECH TENORÓW inwestor zyskuje ekspozycję na wszystkie najważniejsze rynki.

Strona docelowa
http://www.expander.pl/expander2/index.jsp?place=Menu01&news_cat_id=188&layout=4

Warunki wynagradzania Wydawcy
Wydawca jest wynagradzany za przekierowanie unikalnego użytkownika.

0,35 zł za kliknięcie CPC

Afilo prowadzi program partnerski firmy EXPANDER. Istnieje w nim możliwość zapoznania się z ofertą lidera wśród pośredników finansowych z oddziałami w całym kraju. Celem programu jest promocja produktów firmy takich jak:

• inwestycje (plany systematycznego oszczędzania, lokaty, fundusze),
• kredyty mieszkaniowe (nowy kredyt, zamiana na tańszy),
• pożyczka hipoteczna.

Nowy program w modelu CPC jest skierowny do witryn z kategorii nieruchomości. Poprzedni jak pamiętamy oparty był na module LEAD.

Strona docelowa
www.expander.pl

Warunki wynagradzania Wydawcy
Prowizja za przekierowanie unikalnego użytkownika do strony klienta.

PLN 0.35/ unikalny klik

I bought a repeater to get that little extra reach enabling Internet access in the garden. Since I already had a Linksys WRT54G router I thought it would be easy if I also bought a repeater of the same brand. However the easy setup steps as noted in the ‘quick’ installation booklet ‘quickly’ stranded at step 3d with an ’survey failed’ error meaning the wireless router couldn’t find the repeater. Of course I wouldn’t be the first nor the last to encounter such problems and a quick search on the internet gave me the following solution:

1) The network was up and running under WPA secure mode when I did this also I had my pc directly connected via an ethernet cable to the router.

2) Plug expander into wall socket, I did not push config button, don’t pay attention to the lights on the expander.

3) Run an ethernet cable from your router to the expander via the ethernet port below the lights on the expander. //cable included in the WRE54G box

4) Open up 2 browsers on your hardwired computer, one browser at 192.168.1.1 (router) and the second browser at 192.168.1.240 (expander) //password is ‘admin’, leave userid blank

5) Set the SSID and subnet mask on the expander, the same as the router. // <— important the same!!  using the same SSID name will show only 1 wireless network in your wireless connection options however the signal strength of your network will have increased.

6) Go to edit security settings on your expander, type in the security key that is in your router, and save settings on the expander. A couple redlight flashes and you should have two blue ones, your ready to move the expander anywhere to get a signal.

7)If you get a IP conflict when moving the expander, unplug and plug back in // happened to me, besides unplugging I also had to switch on/off the wireless on my laptop.

Thanks to the post here.

On a side note: I’ll be only powering the repeater on when I am in the garden since I already have a cellphone tower nearby emitting enough energy (mW/cm^2, power density) of which the long term effects, if existent, are not clear.

]]> http://glasmagie.wordpress.com/2008/04/29/muttertagsherzen-herzen-aus-glas/ Tue, 29 Apr 2008 21:26:49 +0000 glasmagie http://glasmagie.wordpress.com/2008/04/29/muttertagsherzen-herzen-aus-glas/

Du hast ein Muttertagsgeschenk in meinem Shop gefunden und bis zum 30.04.08 bestelllt? Prima, so habe ich genügend Zeit alles rechtzeitig anzufertigen und zu versenden.

Dafür bedanke ich mich bei den “Frühbuchern” mit einem solchen edlen Glasherzanhänger für Kette, Seiden- oder Lederband (ist nicht dabei), die Euren Bestellungen beiliegen werden.

Die Farbe der Herzen bleibt eine Überraschung.

Ihr könnt sie selbstverständlich auch einfach bestellen.

Wenn ihr eigene Ideen habt, fragt an, ich kann immer nur Anregungen einstellen aber möglich ist viel viel mehr.

Glasmagie Shop

Cu ajutorul acestui programel puteti sa jucati nelimitat, sa schimbati detaliile grafice, rezolutia, dificultatea, etc. Incercati-l sa va convingeti.

DOWNLOAD UEFA EURO 2008 EXPANDER