Keyclone, Not Saving My Settings

[keyclone]

this might seem obvious, but your settings are saved to disk when you hit 'ok' or 'apply'.
hitting the 'x' in the upper right won't save the information (it's the same as cancel)

[Verriit]

I am also having this problem with trying to save my battle.net email info. I am running windows XP and not vista. I did the right click run as admin thing and it still didn't work.... Is there something else I need to try?

[sammler]

Same issue here. Keyclone doesn't like battle.net, huh?
I'm running von Vista, and everything else is saved.
Run-As-Admin or not gives the same result, for keyclone is not installed in a subfolder of any system-folder.
I've tried, though ;-)

Sammler

[neopickaze]

I've never had a problem saving on Windows 7 64bit, always running as administrator, hope you guys figure out what's causing it.

[shaeman]

this might seem obvious, but your settings are saved to disk when you hit 'ok' or 'apply'.
hitting the 'x' in the upper right won't save the information (it's the same as cancel)

If you make any change hit ok or apply. I found when moving around between my command setups that it was a bit erratic as to when information was saved and not.

For example I would go into my commands - and select acc1, I'd enter my battlenet email address. I'd select acc2 and do the same thing. Scrolling back up to acc1 the change wouldn't have been reflected.

hitting Apply or Ok after i changed acc1, then navigating to acc2 and hitting apply or Ok after i made the change ensured the changes were reflected.

One suggestion for improvement (if Rob reads this)- make it obvious if the changes are going to be saved or not.
e.g in the case above. If i make a change to acc1, then go to acc2 a pop up stating
"Do you want to Save changes" Yes or No or something of that ilk.

At least this way you know that the changes you've made will go through.

[keyclone]

changes are only saved when you hit ok or apply. that is the only time they are pushed to disk.

as for battle.net ... yea, that field is on the command editor, but it is not active (should have hidden it... missed it before pushing the release). it will be active on the next release and will save like the other fields.