DonationCoder.com Software > ProcessTamer

ForegroundLockTimeout Value

<< < (2/3) > >>

Scott:
Wait...  I hope you're just setting the ForegroundLockTimeout value once, and not on every run.

mouser:
well in the current version it sets it when (every time) the process tamer tray starts up.
maybe i'll just remove this setting completely from the program and include in the next release 2 little .reg files for people who want to experiment with forcing this value between default value and 0.

war59312:
Glad to see new beta is like that. Since I have no issue. ;)

mouser:
the current version no longer messes with this registry key at all.
and it includes two .reg keys and a little readme for those who want to learn about it and try either setting for other purposes:

"Earlier versions of Process Tamer set the registry value
   HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockTimeout to 0
As described by the Microsoft bulletin for more information:
   http://support.microsoft.com/?kbid=886217
In order to fix a problem where popup windows would lose foreground focus.

Because ProcessTamer now uses baloons to report information, it no longer
 sets this value, and you will find in this directory two registry files,
 which when double clicked will let you set this registry value to wither
 the default value of 200000 or the value described in the windows tweak
 and employed by the original ProcessTamer, 0.

Most people won't care about this or notice any difference, but we are
 providing them for the sake of completeness."

Astara:
Does anyone know if, or how this value relates to information bubbles that pop up when
hovering over taskbar objects?

My bubbles sometimes get into a mode where they come up behind the taskbar, making
them difficult or impossible to read.

Oddly though, it doesn't happen all the time -- seems to be working ok now, but wasn't last night.

Navigation

[0] Message Index

[#] Next page

[*] Previous page