Steema Issues Database

Note: This database is for bugs and wishes only. For technical support help, if you are a customer please visit our online forums;
otherwise you can use StackOverflow.
Before using this bug-tracker we recommend a look at this document, Steema Bug Fixing Policy.



Bug 494 - MouseDoubleClick event breaks the TeeChart PNG exportation in Windows XP
Summary: MouseDoubleClick event breaks the TeeChart PNG exportation in Windows XP
Status: RESOLVED FIXED
Alias: None
Product: .NET TeeChart
Classification: Unclassified
Component: WPF (show other bugs)
Version: TeeChart.NET 2013 4.1.2013.11080
Hardware: PC Windows
: Low normal
Target Milestone: ---
Assignee: Steema Issue Manager
URL: http://teechart.net/directline/viewto...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-02 07:36 EST by sandra pazos
Modified: 2014-01-17 11:04 EST (History)
1 user (show)

See Also:
Chart Series: ---
Delphi / C++ Builder RAD IDE Version:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sandra pazos 2013-12-02 07:36:03 EST
When you work with WPF application and try to export the Chart to png image format, if you call export in the MouseDobleClick appears an exception. 
This problem occurs if you use MouseDobleClick in Windows XP. 
See next code to reproduce the problem:
        public MainWindow()
        {
            InitializeComponent();
            InitializeChart();

        }
        private void InitializeChart()
        {
            Steema.TeeChart.WPF.Styles.Line line1 = new Steema.TeeChart.WPF.Styles.Line(tChart1.Chart);
            line1.FillSampleValues();
            tChart1.MouseDoubleClick += new MouseButtonEventHandler(tChart1_MouseDoubleClick);
        }
        void tChart1_MouseDoubleClick(object sender, MouseButtonEventArgs e)
        {
           tChart1.Export.Image.PNG.Save("C:\\Test.png"); 
        }
Comment 1 christopher ireland 2013-12-09 04:43:45 EST
Could not reproduce this using TeeChart.WPF.dll v.4.1.2013.11081 on WinXP SP3.
Comment 2 christopher ireland 2014-01-17 11:04:10 EST
This issue could be caused by a FocusVisualAdorner added in double-byte WinXP but not any other:

"Rather, it is the child of a
special adorner (FocusVisualAdorner) that is dynamically created by the
keyboard navigation manager."
http://brucezhou1986.wordpress.com/page/4/

check for this type seems to have resolved the problem.