Bug 339904 - Pressing SHIFT key does not go to "Shift" mode
Summary: Pressing SHIFT key does not go to "Shift" mode
Status: RESOLVED INTENTIONAL
Alias: None
Product: kcalc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 2.13
Platform: openSUSE Linux
: NOR minor
Target Milestone: ---
Assignee: Evan Teran
URL:
Keywords:
: 405785 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-10-12 14:28 UTC by Michal Papis
Modified: 2019-04-19 08:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented 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 Michal Papis 2014-10-12 14:28:29 UTC 
when I press CTRL on keyboard the buttons change, this does not happen for SHIFT key, only pressing the "Shift" button allows change of other buttons functions

Reproducible: Always
Comment 1 Evan Teran 2014-10-12 16:24:02 UTC 
The correct shortcut for the "SHIFT" button is "Ctrl+2". I realize that you might expect it to be the Shift button, but I believe (I could be wrong, the decision was made before I got involved) because of internationalization reasons it was assigned to "Ctrl+2" instead.
Comment 2 Evan Teran 2014-10-12 16:24:55 UTC 
Also, re-reading your original report. Just to be clear, the Ctrl button does not "change" any buttons, it is actually showing you the shortcuts required to active that button.
Comment 3 Michal Papis 2014-10-12 16:33:12 UTC 
ok then, how about adding a hint "You are pressing `SHIFT` key, to enter Shift state use `CTRL+2`", there is some space in the notification area, could used for this.

btw is there anything in the commit history showing why would be the SHIFT key wrong/bad?  ... or maybe it's some legacy requirement from old kde and old linux systems?
Comment 4 Michal Papis 2014-10-15 18:49:31 UTC 
Evan so I would like to get response on my questions ^
Comment 5 Christoph Feck 2014-10-25 15:00:26 UTC 
Michal, read bug 318407; it was tried once.
Comment 6 Christoph Feck 2019-04-19 08:32:51 UTC 
*** Bug 405785 has been marked as a duplicate of this bug. ***