A problem of link error in release mode of WTL

Although, it is well compiled in debug mode without any link error, we will see below link error in release mode of WTL.

LIBCMT.lib(tidtable.obj) : error LNK2005: __encode_pointer already defined in atlmincrt.lib(atlinit.obj)
LIBCMT.lib(tidtable.obj) : error LNK2005: __encoded_null already defined in atlmincrt.lib(atlinit.obj)
LIBCMT.lib(tidtable.obj) : error LNK2005: __decode_pointer already defined in atlmincrt.lib(atlinit.obj)
LIBCMT.lib(crt0dat.obj) : error LNK2005: __get_osplatform already defined in atlmincrt.lib(atlinit.obj)

Some typical solution to tackle for this,
1)Set 'Minimize CRT in Use in ATL' to 'NO' in project setting.
   In this case, the size of file will be slightly increased.

2)Or Set 'ignore', the item of 'atlmincrt.lib' in linker option.

How can we reduce the repetitive style declaration in WPF?

Xaml is also needed refactoring. Especially for the style, there is a 'BasedOn' property.
It seems like enum or #define of  c++.

Let's look below xaml code,

   <Style TargetType="{x:Type Label}">
      <Setter Property="FontFamily" Value="Arial" />
      <Setter Property="FontSize" Value="10" />
      <Setter Property="HorizontalAlignment" Value="Right" />
      <Setter Property="FontWeight" Value="Bold" />
   </Style>

   <Style TargetType="{x:Type Button}">
      <Setter Property="FontFamily" Value="Arial" />
      <Setter Property="FontSize" Value="10" />
      <Setter Property="Margin" Value="4" />
   </Style>

In the above code, line 2, 3 and line 9, 10 are exactly the same. In case, by means of  'BasedOn' property, the duplicate can be removed.

  <Style x:Key="defaultControlStyle" 
          TargetType="{x:Type Control}">
      <Setter Property="FontFamily" Value="Arial" />
      <Setter Property="FontSize" Value="10" />
  </Style>
  
  <Style TargetType="{x:Type Label}"
           BasedOn="{StaticResource defaultControlStyle}">
      <Setter Property="HorizontalAlignment" Value="Left" />
      <Setter Property="FontWeight" Value="Bold" />
  </Style>
  <Style TargetType="{x:Type Button}"
           BasedOn="{StaticResource defaultControlStyle}">
      <Setter Property="Margin" Value="2" />
  </Style>

 

 To begin with, 'defaultControlStyle' is declared as a common style, and then each control style are using by 'BasedOn' property.

 

The use of repetitive code is a stairway to overwork in all IT fields.

Why does WPF have strong points in UI programming, when comparing with WINFORM, MFC, WTL ?

• The feature of declarable UI

First of all, the power of WPF is that it can aid to develop impressive user interface faster and easily. We are able to construct the ui of application using a markup language called XAML. The XAML is similar with HTML or XML. So that, if you already have some experience for them, learning XAML will just take a day! Here is an sample short code.

<Window
  xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
  xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
          Title="Hello, there" Height="240" Width="300">
         <DockPanel>
                 <Border DockPanel.Dock="Top" BorderThickness="3" 
                          BorderBrush="White" CornerRadius="5" 
                          Padding="5" Background="Gray">
                     <TextBlock FontSize="10" TextWrapping="Wrap" 
                                Foreground="White">
                     Hello! There.
                     </TextBlock>
                 </Border>
                 <Button Background="LightGray" Width="80" 
                          Height="40" Content="Click"/>
          </DockPanel>
</Window>

Even if you haven't never meet XAML code before, you could estmate what above code is doing.
'DockPanel' and 'Border' are one of a number of rich controls which are provided by WPF. This sample code will make a window like a below picture.

Although, WinForm, MFC, WTL are supporting design tools for constructing UI easily, the quality of default controls of them is not relevant for using real workplace. Actually, the quality of WPF's default controls is also unattractive, but this point can be weighed out by using mark up language, because the use of markup language means that it can be available to bring the feature of web development such as CSS.
 

• The power of Style

For a long time, one of distinct trends in UI programming is to provide the skin function. It allows to change the appearance of the application during the running time. The use of information file such as ini or xml is frequently used as a common method. Here is a drawback.
a typical example is below.

<Skin name="Gloomy">
 <Edit name="Input" position="10,40" size="100,40" color="128,128,128" />
 <Button name="Commit" position="115,40" size="70,40" color="128,128,128" /></Skin>

Above approach requires some extra processes. For example, indicated color value have to be translated relevant value for using in application code. So that, altering skin process usually follows the following sequence.First loading XML, next finding selected skin name, and then  by means of iterating, changing the look of all controls. Furthermore, C++ requires extra library for parsing xml, such as tinyXML.

On the other hand, all approaches for skin function change dramatically in WPF.
To begin with, we can declare some skin set like below,

-DefaultStyle.xaml

<Style x:Key="groupBoxHeader"
           TargetType="{x:Type Borders}">
       <Setter Property="CornerRadius"
                           Value="4" />
         <Setter Property="TextBlock.Foreground"
                           Value="White" />
</Style>

After that, above style set can be used like below code.

<GroupBox.Header>
         <Border Background="{StaticResource brownBrush}"
                Style="{StaticResource gropBoxHeader}">
             <TextBlock Text="Phone" />
         </Border>
</GroupBox.Header>

For changing style during the running time,
1)
After making several style xaml files, when it is needed, load that.
2)
Or, adopt resources to style as a 'DynamicResource'. And then, make each control's syle property to connect  this 'DynamicResource'.

When comparing to other measures, unnecessary works be reduced surprisingly. Now, we can just concentrate to other valuable work.