Bug 80170 - shortcut clash in default settings: [F7]: build active target (kdevelop) and toggle command line (kate)
Summary: shortcut clash in default settings: [F7]: build active target (kdevelop) and ...
Status: RESOLVED DUPLICATE of bug 124384
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: kedittoolbar (show other bugs)
Version: SVN
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-23 07:51 UTC by Daniel Franke
Modified: 2006-04-08 01:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Franke 2004-04-23 07:51:47 UTC
Version:           3.0.90-CVS (using KDE 3.2.1, compiled sources)
Compiler:          gcc version 3.3.1 (SuSE Linux)
OS:          Linux (i686) release 2.4.21-99-default

The default key of "Build active Target" [F7] clashes with kate's default key for toggling the command line. 
Therefore using F7 sometimes brings up kate's command-line interface, sometimes the target is build, maybe both, or nothing happens ... 

Obvious workaround: change default keys.
Comment 1 Jens Dagerbo 2004-04-23 11:32:20 UTC
Sigh. We are never going to be fully rid of this problem. In this case I'm pretty sure we were even using this shortcut before katepart did. Not that the Kate devs would be supposed to know that. Nor could we know that they would decide to use it either.

IMHO, applications that are written as KParts should be somewhat restrictive when defining shortcuts and to the extent that it's sane and possible leave it up to the embedding app to set them. I don't pretend this is a complete solution either though.
Comment 2 F Fracassi 2004-04-23 13:29:14 UTC
I don't know if it is kind of overkill, or even a good Idea from a Security/Stability standpoint, but wouldn't a kind of Hotkey "Registry" Mechanism help to deal with such situations? 

I think of a small lib inside Kdelibs, which handles all shortcuts (KHotkeys?).
Any app (or KPart) would have to register the shortcuts it uses, so that clshes could be detected easily. Each App would then have a (or several) file(s) like "kdevelop.hotkeyrc" where every shortcut and its associated action is declared.
That would help to make Hotkey-Themes, too.

What do you think?
Comment 3 Daniel Franke 2005-01-14 14:31:26 UTC
kdevelop-3.1.91, KDE-3.3.1 (beta1), CVS 050113

[F7] is still used twice as described before, but kdevelop seems to catch it and does not relay it to the kate-part, so the active target is build, the command line is not affected.
Don't know whether this is "fixed" in the ordinary sense ... ?!
Comment 4 Daniel Franke 2006-04-08 01:17:51 UTC
Please close in favour of bug #124384
Comment 5 Jens Dagerbo 2006-04-08 01:26:15 UTC
We might as well... The issue is wider than KDevelop & Kate, but I doubt it should be put to kedittoolbar anyway... Closing as dupe.

*** This bug has been marked as a duplicate of 124384 ***