Hello, this problem does not happen to me however I let someone else use my application for testing purposes and whenever he opens up a window containing the ColorPicker, the application would stop responding.
I have isolated the issue to be related to the ColorPicker only as when I commented out the XAML for it, it was no longer a problem.
I use the ColorPicker in a dialog window which is shown. Everything works fine without the ColorPicker.
System specs of user:
CPU - Intel Core i3-2310M @ 2.10GHz
RAM - 2.00 GB
Type - 64-bit
OS - Windows 7 SP1
Running .NET Framework 4.5
My application is compiled with .NET Framework 4.5 however I am using 4.5.1, unlikely to be the problem.
Comments: ** Comment from web user: JLT93 **
I have isolated the issue to be related to the ColorPicker only as when I commented out the XAML for it, it was no longer a problem.
I use the ColorPicker in a dialog window which is shown. Everything works fine without the ColorPicker.
System specs of user:
CPU - Intel Core i3-2310M @ 2.10GHz
RAM - 2.00 GB
Type - 64-bit
OS - Windows 7 SP1
Running .NET Framework 4.5
My application is compiled with .NET Framework 4.5 however I am using 4.5.1, unlikely to be the problem.
Comments: ** Comment from web user: JLT93 **
Yes. I was just wondering if you can sort of embed the Xceed.Wpf.Toolkit.dll inside the application itself instead of having to share it. If you can't do that then it's all fine, it's not a problem to supply it.