Hotkey settings overwritten on application launch (version 1.5.4.1)

[thatguychase]

I have Audio Switcher (great application, btw) set to start at log in. Something I noticed is my hotkey settings were missing on start-up. I had to change the configuration file to read-only to prevent it from being re-written.

Not a deal breaker, just a minor annoyance.

[xenolightning]

Hmmm, it only clears them if there was an error loading the hotkeys on startup.

Are you able open AudioSwitcher.ini and copy the line that starts with "HotKeys=....."

Thanks

[thatguychase]

Sure:
HotKeys=[112,6,{0.0.0.00000000}.{66ab2a95-2bc6-44eb-90d2-6d59343d39dd}][113,6,{0.0.0.00000000}.{b7075df7-9a01-438e-94b7-ed59529ba63e}]

As of right now, I have to audio outputs that are assigned to Shift+Ctrl+F1 and Shift+Ctrl+F2. Could the number of keys needed pressed be the issue?

Let me know if you need any other information!

[xenolightning]

Strange! It all looks to be ok there.

I've just tried the exact scenario on my laptop. Completely deleted AS, and downloaded a fresh copy to make sure.

What other settings are you using?

And are you able to switch it from non readonly to see what the result is after they hot keys have disappeared? You can copy out your existing settings to save setting the hotkeys again.

Should be something like:
Hotkeys=[] or Hotkeys=

Closing and reopening the application should also cause this issue, so you shouldn't need to restart your pc :)

[thatguychase]

The only other settings I changed were enabling the "Close to Tray" and "Start Minimized" options.

I turned off the read-only on the config and it still overwrote my hot keys. On a hunch, I changed my hot keys to Ctrl+Shift+Q and Ctrl+Shift+W. These seemed to fixed the problem. Maybe it was the combination I was using or the fact the full moon has passed, but it seems to be retain my hot keys.

I'll just mark it down to the full moon. Thanks for your speedy replies!

[xenolightning]

How weird!

I'll give it a go on my desktop when I get the chance. My laptop is a Mac running Windows, so it might be a little different.

I'll close off this bug, feel free to re-open it if you notice it happening again.