Touch for Docking.ToolWindow not fully supported under Win7

Docking/MDI for WPF Forum

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Version: 16.1.0632
Platform: .NET 4.5
Environment: Windows 7 (64-bit)
Avatar

I have problems with touch functionality under Win7. Please use the attached code to reproduce the issue.

The behavior for the ComboBox is that it won't open easily and a selection does not close the dropdown list.

<Window x:Class="WpfApplication7.MainWindow"
        xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
        xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
        xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
        xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
        xmlns:local="clr-namespace:WpfApplication7"
        xmlns:ribbon="http://schemas.actiprosoftware.com/winfx/xaml/ribbon"
        xmlns:docking="http://schemas.actiprosoftware.com/winfx/xaml/docking"
        mc:Ignorable="d"
        Title="MainWindow" Height="350" Width="525">
    <Grid>
        <docking:DockSite x:Name="dockSite"
                          Grid.Column="2" Padding="0" SplitterSize="5"
                          AreDocumentWindowsDestroyedOnClose="False" 
                          UseHostedPopups="False"
                          IsLiveSplittingEnabled="False">
            <docking:SplitContainer>
                <docking:ToolWindowContainer>
                    <docking:ToolWindow x:Name="extendedSidebar"
                            Title="Properties"
                            IsOpen="True"
                            CanAutoHide="True"
                            CanClose="False"
                            CanFloat="False"
                            Padding="6,0,6,0"
                            ContainerDockedSize="500, 200">

                        <StackPanel>
                            <ComboBox>
                                <ComboBoxItem>Test1</ComboBoxItem>
                                <ComboBoxItem>Test2</ComboBoxItem>
                                <ComboBoxItem>Test3</ComboBoxItem>
                                <ComboBoxItem>Test4</ComboBoxItem>
                                <ComboBoxItem>Test5</ComboBoxItem>
                                <ComboBoxItem>Test6</ComboBoxItem>
                                <ComboBoxItem>Test7</ComboBoxItem>
                            </ComboBox>
                        </StackPanel>
                       
                    </docking:ToolWindow>
                </docking:ToolWindowContainer>
                <docking:Workspace>
                    <docking:DocumentWindow BorderThickness="0">
                        
                    </docking:DocumentWindow>
                </docking:Workspace>
            </docking:SplitContainer>
        </docking:DockSite>        
    </Grid>
</Window>

Comments (12)

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hello,

I'm sorry you're having trouble.  I tried this on both Windows 10 and Windows 7 and didn't see a problem though.  I used touch to open the ComboBox and select things.  This was tested with our latest version.  

Also I noticed that you had a DocumentWindow directly as a child of the Workspace.  That hierarchy isn't allowed and I removed it before testing.  You would need a TabbedMdiHost/TabbedMdiContainer in between those if you wanted MDI support.


Actipro Software Support

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Avatar

Hi Support,

thanks for your quick reaction! I don't have access to your latest version. Would it be possible to test this with the version I am using to find out if it has been fixed in between?

Regards
Marcel

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hello,

I just tried v16.1.0632 on Windows 7 too and didn't see a problem either.  The only difference in my sample vs. the one you posted was I removed that DocumentWindow directly within the Workspace.


Actipro Software Support

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Avatar

Hello,

I removed that DocumentWindow without any effect on the behavior. I uploaded my test application, maybe this helps: http://downloads.moduleworks.com/public/C65600279E8043AD8C76D7D3B02DD203.zip

Regards
Marcel

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hello,

I'm sorry but for security reasons we can't run pre-compiled .exes.  Please make a new simple sample project instead that we can open in VS and run.  Thanks!


Actipro Software Support

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Avatar

Hey,

I uploaded the whole solution with the sample project over here: http://downloads.moduleworks.com/public/CA9B2CA106D54448AF8F1E6423A61253.zip

I hope you can handle .zip files.

Regards
Marcel

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Marcel,

I'm running Windows 7 in a Hyper-V VM on a Surface (all our touch devices here have been upgraded to Windows 10 already) and am able to run your sample ok.  Note that since it's in a Hyper-V VM, it's not enabling Aero glass and I don't appear to have a way to test that scenario. 

Are you only seeing this with Aero glass enabled?  What happens if you turn Aero glass support off, like changing your system theme to Aero Basic?


Actipro Software Support

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Avatar

Hi,

I switched to several themes and the bug stays the same. I even tested the "Windows Classic" one. So I would say it's not connected to this.

I uploaded a video of the bug: http://downloads.moduleworks.com/public/3CB3ACAB633445D78C600AF504CA4557.flv

Regards
Marcel

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Marcel,

I believe you indicated you are using an older build of our products.  Can you grab the latest 2017.2 build and see if it still happens in that?  We've made a lot of updates to Docking/MDI over the past year, which is why I ask.  Please let us know.


Actipro Software Support

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Avatar

Hi,

I just checked with an evaluation of your latest build and it works just fine. So it seems this issue got fixed in the meantime. I know we don't have access to your latest build right now so I cannot get rid of the bug.

I will check if it is possible to move to your latest build.

Regards
Marcel

Posted 2 years ago by Actipro Software Support - Cleveland, OH, USA
Avatar

Hi Marcel,

I'm glad to hear it's resolved in the newer builds.  Since you said you were already licensed for 2016.1, you could also try the latest maintenance release of 2016.1 to see if it fixed it as well.


Actipro Software Support

Posted 2 years ago by Marcel Bonzelet - Senior developer, ModuleWorks GmbH
Avatar

Hey,

the latest release of 2016.1 fixed the issue as well!

Thank you very much! I appreciate the quick reactions on this!

Regards
Marcel

The latest build of this product (v2019.1 build 0681) was released 1 month ago, which was after the last post in this thread.

Add Comment

Please log in to a validated account to post comments.