DonationCoder.com Software > ProcessTamer

ForegroundLockTimeout Value

<< < (3/3)

Carol Haynes:
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.
-Astara (July 16, 2006, 06:19 PM)
--- End quote ---

I think that is a bug in windows - the way I get round that is to set windows taskbar not to always be on top - then balloons are on top. I find I can then set the taskbar to be on top again (if that is required) and the balloons still come on top - until the next time.

It is nothing to do with ProcessTamer (I don't have it installed any more since I reinstalled windows but I still get this bug).

app103:
Wouldn't it be better to set a key on first run and check for that key each time it's run?

something like firstrun = 0

And if that key isn't present, change ForegroundLockTimeout back to 200000 and create the firstrun key so you won't have to change it again next time it's run.

Astara:
I think that is a bug in windows ...
-Carol Haynes (July 16, 2006, 06:35 PM)
--- End quote ---

A bug?  In Windows?!?

I'm shocked.

:-)

Carol Haynes:
LOL - shocking but true ;)

I think the best approach Mouser is to ask if earlier versions have been installed (or detect old INI files) and make the change once only after asking permission or use the registry files as you suggested.

neilw20:
My findings:
I had ForegroundLockoutTimeout set to the default: 200000 -- 200 seconds - Heat your lunch and the problem might change??!!
Using timers is just bad programming MS!!
It all started when double click focus - most annoying - started appearing in programs due to multithreading issues.

Anyway, I have a VB.net program I wrote, and it was getting bigger and taking a while to load.
Thought I would be nice, and put up a splash screen.
After running my program, before the splash screen was added, Alt-F4, correctly, would exit my program.
After the splash screen was added, which took owner ship of the desktop, then disappeared as it got overwritten by my application, as it should
my program did not have focus (for 200 seconds!!) and the Alt-F4 offered to do shutdown!! wtf??

Try running regedit. It sits in the back ground, as do some programs.

HKEY_CURRENT_USER\Control Panel\Desktop\ForegroundLockoutTimeout = 0 for me.
I made two .reg files, one to set to zero, and one to restore it.

You need to logout and back in for it to take effect.

And then during testing, if my test/program/think time exceeded 200 seconds, then it looked like I had made a mistake, then it sometimes worked again.
Bloody obscure secret timers!!

I spent a lot more than 200 seconds solving my problems, which should never have existed, if VB.net splash screen was implemented correctly.

All comments, good bad and otherwise appreciated.
Neil

---------contents of .reg file to set it to zero, and my saved value. I always put xxx   :D so I can easily find my changes.
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Control Panel\Desktop]
"ForegroundLockoutTimeout"=dword:0
"ForegroundLockoutTimeoutWas00030d40xxx"=dword:00030d40
end ---------

Navigation

[0] Message Index

[*] Previous page