Tecknomage
October 25th 06, 11:25 PM
In another thread the following statement is made by Paul Pedersen on a
Goggle Group:
--quote--
I've been researching this problem for a couple of days and every fix seen
so far has either not worked or only worked until the next reboot. Many
posts around the 'Net indicated that the problem is created by the taskbar
and tooltips fighting over who gets to be top of the Z order. Logically, it
seemed to me, since the tooltips are "on call" there should be some way to
include a specific "be on top" command to their instructions that would
override the Taskbar's global topmost command during their invocation.
So I read up on the tooltip programming by researching the command strings
found in the registry pertaining to the tooltips. Information found here:
http://blogs.msdn.com/oldnewthing/archive/2005/11/21/495246.aspx
led me here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winu...
which led to the experiment: After backing up (natch!), I made this
regedit:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\VisuÂ*alEffects\TooltipAnimati on]
"SetWindowPos"="HwndInsertAfter, Hwnd_Top"
"SetForegroundWindow"=dword:00000001
The related HKCU values were of the "read defaults" nature so logically,
there had to be some defaults SOMEWHERE - HKLM seemed the reasonable place.
--unquote--
The problem is his Registry entry above does not in the correct format. I
think I can figure out the 2nd entry as...
Name Type Data
SetForegroundWindow REG_DWORD 0x00000001 (1)
....but the 1st line is a mystery.
Can someone translate what the correct format should be for the 1st line?
Goggle Group:
--quote--
I've been researching this problem for a couple of days and every fix seen
so far has either not worked or only worked until the next reboot. Many
posts around the 'Net indicated that the problem is created by the taskbar
and tooltips fighting over who gets to be top of the Z order. Logically, it
seemed to me, since the tooltips are "on call" there should be some way to
include a specific "be on top" command to their instructions that would
override the Taskbar's global topmost command during their invocation.
So I read up on the tooltip programming by researching the command strings
found in the registry pertaining to the tooltips. Information found here:
http://blogs.msdn.com/oldnewthing/archive/2005/11/21/495246.aspx
led me here:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/winu...
which led to the experiment: After backing up (natch!), I made this
regedit:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\VisuÂ*alEffects\TooltipAnimati on]
"SetWindowPos"="HwndInsertAfter, Hwnd_Top"
"SetForegroundWindow"=dword:00000001
The related HKCU values were of the "read defaults" nature so logically,
there had to be some defaults SOMEWHERE - HKLM seemed the reasonable place.
--unquote--
The problem is his Registry entry above does not in the correct format. I
think I can figure out the 2nd entry as...
Name Type Data
SetForegroundWindow REG_DWORD 0x00000001 (1)
....but the 1st line is a mystery.
Can someone translate what the correct format should be for the 1st line?