Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Help-plugin and Keybinder-plugin fighting against F1 hotkey

(1/3) > >>

tiwag:
there is some problem with the hotlkey-assignment when the Help-plugin and the Keybinder-plugin are both activated.

the help-plugin assigns F1 to the default helpfile, while keybinder erases this assignment afterwards (at least on my installation, CB rev 2871, WinXP, wxMSW263p2)
btw. is it somehow possible to specify the sequence order of plugin-loading ?

after Settings->Environment Dialog was opened & closed, the default Help-file is assigned correctly, because the Help-plugin then Reloads the Menu and
assigns F1 to the default help-file.

mandrav:

--- Quote ---btw. is it somehow possible to specify the sequence order of plugin-loading ?
--- End quote ---

No there isn't. No plugin should depend on the initialisation order anyway...

Pecan:

--- Quote ---the help-plugin assigns F1 to the default helpfile, while keybinder erases this assignment afterwards (at least on my installation, CB rev 2871, WinXP, wxMSW263p2)
--- End quote ---

I'm running svn 2869 without this problem. My F1 is bringing up the wxWidgets help just fine.

However, could this be because you've told keybinder to handle the F1 key by previously defining it? If so, just undefine it.

Also, please note that the cbPlugin interface changed to 1.9, so the cbKeybinder{version}.ini reverted to the virgin menu structure with no user keys defined.

You can, for this changed version, simply copy version 1.8 to the version 1.9 .ini file.

If this problem persists for you, could you give me a step-by-step example of how to recreate it? I'll have a look at it when I get home next week.

The description of this problem matches one keybinder had in the original code.   It was walking the menu structure before all the menu keys had been defined, then imposing it's saved disk structure on the menu. Thats why I used to call it zcbKeybinder so it was loaded after all other plugins. I thought I'd fixed that when the AppStartupDone event was created, but it could have crept back in.

A workaround: make sure the key is defined as you like it, check that it's so in the editor->key shortcuts, then save the keybindings.

tiwag:

--- Quote from: Pecan on August 18, 2006, 02:56:08 pm ---However, could this be because you've told keybinder to handle the F1 key by previously defining it? If so, just undefine it.

--- End quote ---
just undefine didn't work, it overwrote the previously assigned setting from the help-plugin with "NO hotkey"


--- Quote from: Pecan on August 18, 2006, 02:56:08 pm ---Also, please note that the cbPlugin interface changed to 1.9, so the cbKeybinder{version}.ini reverted to the virgin menu structure with no user keys defined.
You can, for this changed version, simply copy version 1.8 to the version 1.9 .ini file.
If this problem persists for you, could you give me a step-by-step example of how to recreate it? I'll have a look at it when I get home next week.

--- End quote ---
i tried several things and finally i got rid of this bug, when i deleted manually all lines in cbKeyBinder04v19.ini
which referenced the helpfiles. now the setting which is set-up by the help-plugin is persistent.

it looks like that the KeyBinder plugin "erases" the hot-key when you just undefine it ;)

thx Tiwag

Pecan:
tiwag,

Would you describe the order in which plugins are loaded for you.
Could you also describe your help file settings.
I'd like to try and re-create this situation.

thanks
pecan

Navigation

[0] Message Index

[#] Next page