Hello,
our application allows the user to switch docking settings around. To do so, the user can click a tool in a toolbars manager's toolbar.
At the moment the user clicks the tool, the system recognizes a click on the desktop while/after/before LoadFromXML is running.
Commenting LoadFromXML out will result in clean behavior.
On slow machines if the user clicks the tool and a desktop icon is behind at this desktop's location, the desktop icon will be visible for a brief period of time, which is kind of irritating :)
On fast machines you will not see the icon but if you minimize the application and bring the tool and the desktop icon together to overlap, you can see the selection of the deskop item (less than 1 second). You are unable to open/run the desktop item by double clicking the tool, I tried that :)
I would like to get rid of this behavior, any advice?
Blue
Hello Blue,
I am not able to reproduce this behavior, so could you please try to attach, if possible, a small sample project, reproducing the above mentioned issue(with the steps to reproduce it), I will be happy to take a look at it?
Hello Boris,
thanks for your answer and attempt.
I am on version 11.2.20112.2128 btw. I will try to build an example for you. Lets hope I can rebuild to make this issue appear.
Blue,
Thank you for your feedback. I've been trying this with different styles, themes, versions, clicking the first, the second button, both in a row, double-clicking them pretty fast and was not able to reproduce the issue even once.
I know it might be hard for you, if you have not done it, is it possible to test this with a fresh installation of Win7 without any modifications and alternations of anything? I have the strange feeling that this might be coming somehow from the Personalization of the Operation System, but how can I tell for sure when after so many attempts I have failed.
Hey Boris,
Have you tried this on different machines yet? Maybe it's just your system that this issue doesnt occur.
We are going to try out fresh install. Stay tuned,
I tried on two other different machines and I was not able to reproduce the issue. Did you have time to test it on your side?
not yet, I passed the task to one of our testers, they are not working full time, but I will talk to him to rank it top.
I will be waiting for your feedback on this. I will be very glad to assist you, if there is any way for you to find some steps to reproduce this issue.
Thank you
I created the following case for you: 'CAS-112231-H0J0M6' and will update you through it.
Hello again,
we just tried it on a clean windows 7 professional installation.
we installed dotnet 4.5 to run the example application.
The behavior was the same.
As a side note or hint: we recently experimented with SendMessage and LockWindowUpdate user32.dll API functions for a totally different scenario. If you use those functions to prevent a form from drawing, you get the same result as shown in the video. We had to skip that approach and found another solution to solve that issue, but it might be related to this one in case you internally make use of this kind of functions.
unfortnuately not, but I still after it. Stay tuned.
Did you have the time to try that on a clean Windows 7 installation?