release thread - keyclone v1.8k

[Ken]

I found a bug:
When saving and loading the maximizer settings where the different windows have a key with a modifier(add, lshift-add, ctrl-add, lshift-ctrl-add) it discards the modifiers when loading the data back in.
So on each window it just appears as 'add'.

I always encounter a bug when exit on vista x64... everything seems to exit fine but if I try to relaunch Keyclone a 2nd time it says that another instance of keyclone is already running ...

You're not supposed to run keyclone on the same machine twice. I can't see why you would want to do that.

another bug when keyclone is sent to the tray .. no way to let get out .. only way is to force quit it by ctrl-alt-suppr

that's a lot of bug for a new release ...

I have a similar problem on my x64 Windows XP. Keyclone is a 32 bits application and it hasn't been tested on a x64 bit platform yet. Have patience, the developer told me he's going to get an x64 machine.

[keyclone]

When saving and loading the maximizer settings where the different windows have a key with a modifier(add, lshift-add, ctrl-add, lshift-ctrl-add) it discards the modifiers when loading the data back in.
So on each window it just appears as 'add'.

please re-word / re-explain ...

@king.pa
yes, the hang-on exit bug has already been reported. you can exit cleanly by right-click the tooltray icon and select exit

a second keyclone will not run as long as another is in memory... unless you specifically allow for it under keyclone/setup/misc/able-to-run-multiple-keyclones

[Ken]

please re-word / re-explain ...

A minimal set to reproduce:
1) Set up maximizer and create 2 regions
2) Bind the following keys to the regions: add(+), shift-add
3) Save maximizer settings to a file
4) Load these settings back into keyclone
5) Observe how the keybinds to the regions now both are: add, add
There is not shift-modifier anymore on the second region.

[keyclone]

ahh... i see it. the PiP hotkey loses its modifier when importing

this has been fixed and will be available in the next release