Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development
BrowseTracker plugin
MortenMacFly:
--- Quote from: eranif on July 22, 2007, 10:56:23 pm ---I am capturing OnNavigationKey event
--- Code: ---void wxFlatNotebook::OnNavigationKey(wxNavigationKeyEvent& event)
--- End code ---
which seems to react for these two combinations (Ctrl + PgUp/Dn & Ctr+Tab+(Shift)), so I guess this comes from the system settings, but I really dont know from where or how to change this.
--- End quote ---
Ah - ok... good to know. At least that's the starting point for further "research"... ;-) Thanks!
Pecan:
--- Quote from: MortenMacFly on July 23, 2007, 10:10:54 am ---
--- Quote from: eranif on July 22, 2007, 10:56:23 pm ---I am capturing OnNavigationKey event
--- Code: ---void wxFlatNotebook::OnNavigationKey(wxNavigationKeyEvent& event)
--- End code ---
which seems to react for these two combinations (Ctrl + PgUp/Dn & Ctr+Tab+(Shift)), so I guess this comes from the system settings, but I really dont know from where or how to change this.
--- End quote ---
Ah - ok... good to know. At least that's the starting point for further "research"... ;-) Thanks!
--- End quote ---
http://developer.berlios.de/bugs/?func=detailbug&bug_id=11348&group_id=5358
That are actually defined by the OS as the "minor control navigation keys". They are sent to wxControlContainer, and from there to any class using the navigation event.
MortenMacFly:
--- Quote from: Pecan on July 23, 2007, 01:38:39 pm ---http://developer.berlios.de/bugs/?func=detailbug&bug_id=11348&group_id=5358
That are actually defined by the OS as the "minor control navigation keys". They are sent to wxControlContainer, and from there to any class using the navigation event.
--- End quote ---
Thanks for that info. Well, we have a conflict now: Two functionalities fight for a hotkey. Which one is right? Both has to do with navigation. The pro for wxFNB is that it's "wxWidgets native" then, the pro for jumping to next/previous method is being compatible with major other IDE's (like Visual Studio). Which do we want?
With regards, Morten.
Ps: Can the keybinder plugin handle any re-association?! (I guess no.)
Pecan:
--- Quote from: MortenMacFly on July 23, 2007, 02:13:58 pm ---Ps: Can the keybinder plugin handle any re-association?! (I guess no.)
--- End quote ---
If a plugin changes a keybinding on the menu items, keybinder will recognize and record it withing 15 seconds.
But....
Since wxFlatNotebook is invoked before the plugins, it owns the navigation keys first. Since the OS hands it off to the navigation events.
Since the CC plugin gets invoked later...
CC could then (as it does now) intercept the wxEVT_NAVIGATION_KEY if an option box is checked.
But the user will have to give up the OS "minor navigation control keys".
It seems Visual Studio users find that acceptable.
When in doubt, give the user the option.
MortenMacFly:
--- Quote from: Pecan on July 23, 2007, 02:52:00 pm ---CC could then (as it does now) intercept the wxEVT_NAVIGATION_KEY if an option box is checked.
--- End quote ---
It can't really. I have added a listener to this event in CC and it never gets called. This is because simply wxFNB "steals" this event already. I didn't realise this until now as I have switched to wx28 (in wx26 this worked properly). Now the CTRL+PGUP/PGDOWN simply is ignored for CC. This very much deceases my productivity... :-(
I guess we *have* to think either of making this optional in both, wxFNB and CC (which is a bad idea IMHO) or disabling this functionality in on of both and enabling it in the other (which is bad, too) or change the hotkeys for CC or wxFNB.
For now I have disabled the Event in wxFNB (for me only) to be able to "method jump" again... But what makes me wonder: Why is it actually woiring in wx26? Did that mean the the event interception of wxFNB was ignored there?!
With regards, Morten.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version