I couldn't agree more :lol:
If something like that gets implemented, I'll love to see it available as a standalone too, so we could use it in other projects appart from C::B.
Making it a wx contrib, and perhaps calling it wxCommandBinder or wxActionBinder. :P
I just hope you have time to work on it ;)
A better way, I think, is for C::B to be the "server" for a bunch of
keybinder type plugins. C::B could provide the services AND
verifications/validations
...Have commited KeyBinder v0.4.8 (svn 1708)...you've used wxMenuItem::SetFont & ::GetFont
menuutils.cpp: In member function 'void wxMenuCmd::RebuildMenuitem()':
menuutils.cpp:162: error: 'class wxMenuItem' has no member named 'SetFont'
menuutils.cpp:162: error: 'class wxMenuItem' has no member named 'GetFont'
I should have surrounded that routine with #if defined( __WXMSW__ )i fear, that will not be enough ...
i fear, that will not be enough ..
Have commited KeyBinder v0.4.10 (svn 1719)
Separated out and demangled the GTK menuutils::Update()
menuitem update code.
//memorize the key file name as {%HOME%}\cbKeyBinder+{vers}.ini
m_sKeyFilename = ConfigManager::GetConfigFolder();
// remove the dots from version string (using first 3 chars)
wxString sPluginVersion=m_PluginInfo.version.BeforeLast('.'); //+v0.4.1
sPluginVersion.Replace(_T("."),_T(""));
m_sKeyFilename = m_sKeyFilename<<wxFILE_SEP_PATH<<m_PluginInfo.name<<sPluginVersion
<<_T("v")<<SDKverStr<<_T(".ini"); //+v0.4.1
but there exists another problem, i can't save any new keyboard settings,
after applying the changes, keybinder pops up a messagebox, saying the
new keyboard layout is saved under "/home/tiwag//.codeblocks/cbKeyBinder04v16.ini"
but there is no such file existing :?
did you notice the double slashes in the directory-path /home/tiwag//.codeblocks ?
it seems, that thisCodehas to be handled differently in win32 and unix OS's//memorize the key file name as {%HOME%}\cbKeyBinder+{vers}.ini
m_sKeyFilename = ConfigManager::GetConfigFolder();
// remove the dots from version string (using first 3 chars)
wxString sPluginVersion=m_PluginInfo.version.BeforeLast('.'); //+v0.4.1
sPluginVersion.Replace(_T("."),_T(""));
m_sKeyFilename = m_sKeyFilename<<wxFILE_SEP_PATH<<m_PluginInfo.name<<sPluginVersion
<<_T("v")<<SDKverStr<<_T(".ini"); //+v0.4.1
HTH
tiwag
I am aware that keybinder is broken with the new "settings scheme" in svn 1838.Ah yes, I only just finished that one... :lol:
I am aware that keybinder is broken with the new "settings scheme" in svn 1838.Ah yes, I only just finished that one... :lol:
Ah yes, I only just finished that one... :lol:
Very cool icon, but you might want to replace that "Strg" key with one that appears on more keyboard layouts. I've only ever seen Strg keys on German keyboards1. Using another key would make it more recognizable to more people, I think.Funny, now that you mention it, I have been wondering for many years why the "control" key is not labelled "control" on PC keyboards... buf of course I haven't used an English keyboard in a decade, so I wouldn't remember :)
Maybe Alt?
Very cool icon, but you might want to replace that "Strg" key with one that appears on more keyboard layouts. I've only ever seen Strg keys on German keyboards1. Using another key would make it more recognizable to more people, I think.Funny, now that you mention it, I have been wondering for many years why the "control" key is not labelled "control" on PC keyboards... buf of course I haven't used an English keyboard in a decade, so I wouldn't remember :)
Maybe Alt?
Macintosh calls it "control", I think.