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

Help-plugin and Keybinder-plugin fighting against F1 hotkey

<< < (2/3) > >>

tiwag:

--- Quote from: Pecan on August 19, 2006, 05:18:43 am ---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


--- End quote ---

1. start CB (enable keybinder and help plugins)
2. assign your default help-file (F1) using the help-file-plugin (file A)
3. close CB
4. delete your cbKeyBinder04v19.ini file
5. start/close and restart CB (so that keybinder will generate a new cbKeyBinder04v19.ini file )
6. change the assignment of your default help-file (F1) using the help-file-plugin (File B),
7. close and restart CB
8. i get the settings restored from keybinder plugin, F1 is assigned to File A
9. Open Settings->Environment Dialogue, and close it.
10. now i get the settings restored from helpfile plugin, F1 is assigned to File B

my order of plugin loading is as follows:

--- Code: ---Found 23 plugins
Loading: CodeStatistics BYOGames EnvVars CBProfiler ClassWizard CodeCompletion Autosave Compiler Debugger FilesExtensionHandler DevPakUpdater Source Exporter HelpPlugin cbKeyBinder ToDoList wxSmith wxSmithMime wxSmithWizard AStylePlugin copystrings DragScroll ScriptedWizard CB_Koders CodeSnippets

--- End code ---

thomas:

--- Quote from: mandrav on August 18, 2006, 02:17:17 pm ---
--- 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...

--- End quote ---
Yes there is!  Rename help_plugin.dll to zhelp_plugin.dll  8)

Hey, don't laugh... back in the good old days when the meadows were green, the beer was strong, the Hobbits cheerish and plentiful, and Macs did not suck so bad as they did after the introduction of PowerPC CPUs, this was the "standard" procedere to manage your two screen rows of extensions :)

tiwag:

--- Quote from: tiwag on August 18, 2006, 09:32:05 pm ---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.

--- End quote ---
this doesn't work, the keybinder plugin reports a erroneus ini file later on, when i try to assign another shortcut ...

the only workaround is to set the F1 hotkey with keybinder-plugin to exactly the same file as used in the help-plugin.

tiwag:

--- Quote from: thomas on August 19, 2006, 11:49:27 am ---
--- Quote from: mandrav on August 18, 2006, 02:17:17 pm ---
--- 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...

--- End quote ---
Yes there is!  Rename help_plugin.dll to zhelp_plugin.dll  8)

Hey, don't laugh... back in the good old days when the meadows were green, the beer was strong, the Hobbits cheerish and plentiful, and Macs did not suck so bad as they did after the introduction of PowerPC CPUs, this was the "standard" procedere to manage your two screen rows of extensions :)

--- End quote ---

you're right, but it doesn't help in this particular situation,
keybinder plugin seems to override the help-plugin settings even when the help-plugin is loaded after the keybinder-plugin.

this is not nice, but at least the workaround with setting the F1 shortcut twice,
once with help-file plugin and once with keybinder-plugin works...

thomas:
Well, one could still register to EVT_APP_STARTUP, then start a 500ms timer and set the F1 hotkey as soon as the timer fires  :shock:

Navigation

[0] Message Index

[#] Next page

[*] Previous page