I'm guessing that the problem happens when the debugger initializes it's default keys *after* keybinder has already loaded the keybinding.
If a plugin resets its keys after the key bindings are already loaded, KeyBinder records the new keys within 15 seconds.
Instead, increase KeyBinder's priority, so it is loaded first.
Actually I might be wrong about the loading order being a problem.
KeyBinder is loading its bindings on the cbEVT_APP_STARTUP_DONE event.
I thought that would be the right place to do it. I was thinking that all the plugins would have been loaded by then, and they would have already set their menu command keys. Then keyBinder would re-set them to the users bindings.
I cannot figure out how the debugger could be "resetting" the command keys after EVT_APP_STARTUP_DONE.
But once it does, keyBinder will record them within 15 seconds.
Of course, I could be all wet about all this guessing.
Secondly, I cannot seem to recreate the problem with my collection of plugins, so I'm updating Ubuntu to wx2.8.4 today and will try to re-create the problem with the nightly.
Thanks for the suggestion.
Oh, and where do I do a priority modification?
Wouldn't keyBinder want to be the lowest priority so it gets loaded last in order to do the "final" key settings?