Wayne Bradney
Всего сообщений: 5
Дата регистрации: 01.04.2011
|
Создано:
01.04.2011 13:11:04
|
 |
For an application that makes use of ApplicationId to "stack" windows on the Windows 7 TaskBar, the wrong icon gets displayed when the app is pinned to a secondary monitor's taskbar, and then an application window with a different icon is moved to that monitor while the main app window is elsewhere. At least, the behaviour is inconsistent with the Windows 7 taskbar.
To reproduce:
- Open an app that "stacks" its windows on the Win7 TaskBar (eg. Outlook) - Move the Outlook window to the primary monitor if it's not already there - Right click the Outlook taskbar icon and pin it to the primary taskbar - In Outlook, do File->New->Mail Message. The new icon appears "stacked" under the Outlook icon on the primary taskbar (as expected) - Move the Message window to a secondary monitor. The new message icon appears on the secondary taskbar (as expected) - Move the Outlook window to the same secondary monitor. On the secondary taskbar the new message icon again stacks under the Outlook icon (as expected) - Pin Outlook to the secondary taskbar
Now, Outlook should be pinned to both taskbars.
If you move the New Message window to the primary monitor and the Outlook window to the secondary monitor, both taskbar icons remain the Outlook icon (as expected).
However, if you move the New Message window to the secondary monitor and the Outlook window to the primary monitor, the icon on the primary taskbar remains the Outlook icon, while the icon on the secondary taskbar becomes the New Message icon (not expected - it should remain as the pinned app's icon, like it does on the primary taskbar).
I hope this makes sense...
|
Vasiliy Ivachev
Администратор
-retired-
Всего сообщений: 2073
Дата регистрации: 09.11.2010
|
Создано:
03.04.2011 21:58:12
|
Hello Wayne,
Thanks for the post.
The problem has been confirmed.
We'll try to fix it.
Best regards.
|
Alex Fadeyev
Администратор

Moderator
Всего сообщений: 1452
Дата регистрации: 30.09.2005
|
Создано:
23.01.2012 23:51:58
|
Wayne, the problem appears to be fixed in the recent 7.0 beta 1/4.0 beta 2 (whichever product you are using). Please could you confirm this?
|