Move eventFilter from contextbrowser into kate

[David Nolden]

Am Montag, 10. November 2008 20:35:12 schrieb Andreas Pakulat:
> You don't need a filter for that, as you can simply choose to "do nothing"
> when the action is executed. So you could check wether the view is a KTE
> and wether there's a code-browser toolview visible. Another issue with an
> eventfilter implementing shortcut logic is that the user doesn't get warned
> about conflicts. Especially when Alt+Arrows/Enter is implemented this is
> something that might happen easily. There's been a lot of effort done in
> kdelibs to make sure that users don't end up with conflicting shortcuts and
> even if they do so, that they at least get a warning.
But don't ambiguous shortcuts block each other? I've noticed when hacking on 
the shortcut in kate, that keys that are bound through KAction neither ever 
reach the QObject::event() function, nor any event-filter.

This would work if kate would be the only entity using these shortcuts, which 
would need one more interface to notify kdevelop of the shortcuts.

Greetings, David