03-27-2021, 02:58 PM
Not sure I can reproduce it.
Tested on Windows 10, current version. Toolbar1 - attached to taskbar. Toolbar2 - not attached.
At first tested with QM Options -> Run as = Administrator. It is default.
Results:
- Toolbar1 always on top of taskbar; when taskbar clicked, briefly not on top. It is normal.
- Toolbar2 not on top after taskbar clicked. It is normal. Then right click toolbar and check "On top of topmost windows". Climbs on top after several seconds. It is normal.
Then tested with QM Options -> Run as = uiAccess.
Results:
- Toolbar2 always on top, even when taskbar clicked. I guess it is how was in previous QM versions. But actually it isn't normal. It is just one of Windows bugs or undocumented features.
In previous QM versions, when selected Run as Administrator, QM actually is Administrator + uiAccess. And Windows in some cases works differently when with uiAccess. In most cases it is undocumented. In QM 2.4.12, when selected Run as Administrator, it is Administrator without uiAccess. Because Windows has too many problems with uiAccess.
Tested on Windows 10, current version. Toolbar1 - attached to taskbar. Toolbar2 - not attached.
At first tested with QM Options -> Run as = Administrator. It is default.
Results:
- Toolbar1 always on top of taskbar; when taskbar clicked, briefly not on top. It is normal.
- Toolbar2 not on top after taskbar clicked. It is normal. Then right click toolbar and check "On top of topmost windows". Climbs on top after several seconds. It is normal.
Then tested with QM Options -> Run as = uiAccess.
Results:
- Toolbar2 always on top, even when taskbar clicked. I guess it is how was in previous QM versions. But actually it isn't normal. It is just one of Windows bugs or undocumented features.
In previous QM versions, when selected Run as Administrator, QM actually is Administrator + uiAccess. And Windows in some cases works differently when with uiAccess. In most cases it is undocumented. In QM 2.4.12, when selected Run as Administrator, it is Administrator without uiAccess. Because Windows has too many problems with uiAccess.