This project has moved. For the latest updates, please go here.

ChildWindow Title Bar in windows 8

Apr 25, 2014 at 12:00 PM
Edited Apr 28, 2014 at 6:44 AM
Hi,

I have problem with childwindow title bar in windows 8.

Image

http://s22.postimg.org/iy848g7o1/Windows_7_Style.jpg

its working fine in windows 7 as show in the above image.

Image
http://s21.postimg.org/5w0vvl9o7/Windows_8_Style.jpg

Please let me know how to get rid of the Blue title bar in window 8.

XAML i have used ....
 xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" IsModal="True"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" WindowStartupLocation="Center"
         xmlns:xctk="http://schemas.xceed.com/wpf/xaml/toolkit" WindowThickness="0"
         WindowStyle="None"  BorderThickness="0" BorderBrush="#3399cc" 
         Background="#9eceec" Closing="ChildWindow_Closing" KeyDown="Window_KeyDown"
Developer
Apr 28, 2014 at 12:37 PM
Hi,

I'm using v2.1 of the toolkit with windows8 and I don't see the title bar. Here's my complete XAML and the resulting image :
<xctk:WindowContainer x:Name="_windowContainer">
         <xctk:ChildWindow x:Name="_childWindow"
                           Caption="My ChildWindow"
                           IsModal="True"
                           WindowStartupLocation="Center"
                           WindowState="Open"
                           WindowThickness="0"
                           WindowStyle="None"
                           BorderThickness="0"
                           BorderBrush="#3399cc"
                           Background="#9eceec">
            <StackPanel>
               <TextBlock Text="This is a regular Child Window"
                          Padding="10" />
               <CheckBox Content="MyCheck" />
            </StackPanel>
         </xctk:ChildWindow>
</xctk:WindowContainer>
http://s14.postimg.org/j271fpkxd/child_Window.jpg
Marked as answer by bvpavan on 5/6/2014 at 3:33 AM
May 6, 2014 at 10:34 AM
Edited May 6, 2014 at 10:35 AM
Thanks for your reply..it seems that issue has been addressed in v2.1.