https://bugs.kde.org/show_bug.cgi?id=402760
Simone Gaiarin changed:
What|Removed |Added
Resolution|--- |FIXED
Status|CONFIRMED
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #20 from Simone Gaiarin ---
Regarding Alt having already the function of the tooltip, that is true, but on
the other hand that function is used only when the user interact with the
keyboard, so that the user does not even notice that Alt is
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #19 from RJVB ---
I hesitated suggesting to use Alt exactly because it already has the tooltip
function, and on Linux and MSWin it also serves as a menu activator.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #18 from Simone Gaiarin ---
To fully reply to you. There is indeed a standard shortcut to activate source
browse mode. Though, I think that having a quick modifier to enable it for a
second while clicking is not bad (this bug let me discover
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #17 from Simone Gaiarin ---
Alt is already used to show the tooltip as documented here:
https://userbase.kde.org/KDevelop5/Manual/Working_with_source_code#Exploring_source_code
Moreover, both Ctrl and Alt achieve the same effect of letting
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #16 from RJVB ---
That doesn't look like it's a shortcut that could be put in the list of
configurable shortcuts?
Frankly, who's idea was it to use the Ctrl key for this feature? It seems
evidently inavoidable that this would lead to unwant
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #15 from Simone Gaiarin ---
Some thoughts from my debug session:
The culprit is in browsemanager.cpp, method eventFilter (Kdevelop at tag 5.3.2)
When the Ctrl key is pressed, we enter the first 'if' (line 178) because
keyEvent->key() == br
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #14 from RJVB ---
That's great to know because plugin enabled/disabled state info is per-session,
meaning you can keep the python plugin disabled except in sessions dedicated to
python development.
(Sadly it's a bit hit-and-miss to predict
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #13 from Simone Gaiarin ---
Disabling the plugin "python support" and restarting KDevelop solves the
problem.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #12 from RJVB ---
Interesting. Did you check if just disabling the plugin from the global
settings dialog is enough to make the issue go away (immediately or after
restarting KDevelop)?
--
You are receiving this mail because:
You are watch
https://bugs.kde.org/show_bug.cgi?id=402760
--- Comment #11 from Simone Gaiarin ---
The bug is in kdev-python. Uninstalling that package the problem goes away
(reason why I could not see the problem in the compiled version of KDevelop,
because it was not loading kdev-python correctly).
--
You a
https://bugs.kde.org/show_bug.cgi?id=402760
Simone Gaiarin changed:
What|Removed |Added
Assignee|kdevelop-bugs-n...@kde.org |m...@svenbrauch.de
Product|kdevelop
12 matches
Mail list logo
