Bug 369418 - Shortcuts for Kdevelop Handbook and What's this always overwrite setting
Summary: Shortcuts for Kdevelop Handbook and What's this always overwrite setting
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: Profiles (show other bugs)
Version: 5.0.1
Platform: Appimage Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-27 13:17 UTC by Ian H
Modified: 2022-10-27 12:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ian H 2016-09-27 13:17:37 UTC 
i have f1 set to 'find uses' , and unset kdevelop handbook and what's this so that there isnt a conflict when using f1. 

Every time i restart kdevelop, those two unset settings go back to defaults.

Reproducible: Always

Steps to Reproduce:
1. Unset 'Kdevelop Handbook' and 'What's This?' in configure shortcuts
2. restart kdevelop
3. open configure shortcuts again

Actual Results:  
Kdevelop Handbook setting is back at f1 and What's this? is back at Shift+f1.

Expected Results:  
the two settings should still be unset
Comment 1 Ian H 2016-12-16 19:29:53 UTC 
if i were to take a look at fixing this, where should i look? i did some searching in the source code but i never could find anything that seemed related to this. Maybe it is just built into kde?
Comment 2 Kevin Funk 2016-12-16 20:19:37 UTC 
The shortcuts are from kconfig.git:

% ag F1 kconfig/src/gui/kstandardshortcut.cpp
126:    { Help, "Help", QT_TRANSLATE_NOOP3("KStandardShortcut", "Help", "@action"), Qt::Key_F1, 0, QList<QKeySequence>(), false },
127:    { WhatsThis, "WhatsThis", QT_TRANSLATE_NOOP3("KStandardShortcut", "What's This", "@action"), SHIFT(F1), 0, QList<QKeySequence>(), false },

I'm not sure where/how to fix this issue, to be honest
Comment 3 Justin Zobel 2022-10-27 02:48:59 UTC 
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Ian H 2022-10-27 12:54:31 UTC 
seems to be working in the latest version