[Release] GammaControl v1.8

**0l33l** · 09-26-2005, 02:32 AM

New in this version:

Fixed resume bug... finally tested.

Notes:
If you get a "Class not registered error" then that means that you do not have map monkey installed or fully registered. Uncheck that option in the config.

Oh, and don't forget to run config.

Also, don't forget to donate

Download v1.8 Now!

**0l33l** · 09-26-2005, 02:37 AM

I'll be out of town till friday (damn mandatory school trip

), so I expect a large list of bugs (hopefully not) and feature requests.

Donations are motivating for continuing development

**justintime** · 09-27-2005, 09:55 PM

Thanks ol33l. Installed, and will test tomorrow morning to see what happens after resume!

**justintime** · 09-28-2005, 08:37 PM

Bad news. According to my testing, it does not play well with Hibernation

**jbyers** · 09-29-2005, 10:15 AM

After resuming from Hiber it still stayed in night mode from the previous evening. Any ideas???

**justintime** · 09-29-2005, 11:16 AM

In many ways, 1.7 worked better. It had the resume bug, but at least it didn't do some odd stuff that 1.8 is doing.

I have noticed that 1.8:

1) Does not switch settings after hibernate, and
2) Doesn't play well with CF after hibernate (after trying to manually force the correct setting through the config window og GC, it tends to switch to a darker gamme anyways after CF loads... this happens only after resume. 1.7 didn't exhibit this behaviour)

**0l33l** · 10-01-2005, 03:33 AM

Damn bugs

I actually did hibernation testing and it send me a message that it would update the gamma.

My guess: windows won't accept change gamma messages the second it resumes.

**justintime** · 10-01-2005, 08:22 AM

Originally Posted by 0l33l

Damn bugs

My guess: windows won't accept change gamma messages the second it resumes.

But I thought GC would check every few minutes, no? So even if it fails to change it the second it resumes, why wouldn't it change the gamma a few minutes later on the next 'check'?

Also, I am starting to think this has to do with CF itself.... ITest it out with CF Launched. There's something odd going on with the internal CF gamma switching. Perhaps CF does it's own Gamma Check upon resume? I haven't quite honed in on the issue, but I am noticing CF interferes with GC.

**0l33l** · 10-01-2005, 06:52 PM

Originally Posted by justintime

But I thought GC would check every few minutes, no? So even if it fails to change it the second it resumes, why wouldn't it change the gamma a few minutes later on the next 'check'?

Also, I am starting to think this has to do with CF itself.... ITest it out with CF Launched. There's something odd going on with the internal CF gamma switching. Perhaps CF does it's own Gamma Check upon resume? I haven't quite honed in on the issue, but I am noticing CF interferes with GC.

Well, i stopped checking every few min because it was flooding some of the SDKs. Plus it wasn't "proper" code. It made my program act as if it was written in VB

Maybe it is CF. I don't know. I don't use it.

**justintime** · 10-01-2005, 06:57 PM

ol33l: So have you tested and confirmed that if you hibernate at NIGHT, and resume during DAY, it will switch over correctly?

You said you tested (earlier post), but not sure under what scenario!

I love this utility, I am so frustrated it won't work correctly though. This is my number one 'support software' in my carPC