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
Thank you
Blue,
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?