Do you know what version this started happening with? If you change the key combination for a default hotkey does it get reset as well, or just the custom hotkeys?
Are you using any sort of software such as DeepFreeze that reverts your registry to previous versions overnight / during sleep?
I am I.
You didn't by chance run CCleaner in between these instances, did you?
I am I.
PeterDackers
44 discussion posts
Hi John, sorry for the late reply, and no. I mainly run CCleaner once a week, just before I make an image of my hard disk.
I even tried a fresh install of Vista Home Premium, but to no avail. It still resets the custom hot-keys after a reboot.
OK, I'll set some hotkeys in Windows 7 and see if it is resetting after reboot here.
I am I.
PeterDackers
44 discussion posts
Thanks, curious as to what you'll find.
Nothing so far. THey haven't reverted....
Which keys are you changing? I'll change those - since Win7 has built in app movement from monitor to monitor, I now stopped changing the DF keys.....
I am I.
I created 2 of them, test1 and test 2. Let's see if this causes any problems.
I am I.
I just want to make sure I understand the setup here, as I've been unable to reproduce this problem so far:
- Windows Vista or Windows 7 (but not XP)
- Running as a user account, with UAC enabled
- All DisplayFusion settings get saved correctly except for the HotKeys (correct?)
Do the HotKeys only get reset on reboots, or does it happen when you exit and then re-launch DisplayFusion as well?
John & Peter: I have sent you both a PM with a link to a test build, if you would like to give it a try. It is still marked as version 3.0.2, but it has some fixes in place to hopefully prevent the HotKeys from being reset. Thanks!
You've got PM, Jon.
Peter - yes, pseudo means fake, or some reasonable facsimile thereof. I write a lot of pseudo-code in my Analysis of Algorithms class, so I was attempting to make a joke.
Since Jon has sent out test builds, I suppose this is in fact a rel bug - Kudos, Peter, for discovering it.
I am I.
This issue has been fixed in version 3.0.3 which will be released in the next few days. Thanks!