Launchpad has imported 27 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=344638.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2015-02-27T19:37:56+00:00 Harald-pollak wrote:

Input from standard keys ( keysym as written by xev: 0x31, 1 ) works
fine, the number 1 is displayed in the display, but when i press the
number 1 on my numerickey pad ( xev: 0ffb1, KP_1 ) nothing happens in
the display.




Reproducible: Always

Steps to Reproduce:
after kcalc started
1. press 1 from standard keyboard
2. press 1 from numeric keypad

Actual Results:  
1. 1 is displayed correctly
2. nothing happens

Expected Results:  
1. 1 is displayed
2. 11 is displayed

It tried to make a quick and dirty test in the code ( inside void
KCalculator::keyPressEvent(QKeyEvent *e) ):

I added:

std::cout << "Key pressed: " << e->key() << std::endl;

if (e->key() == Qt::Key_1) {
            pb1->animateClick();
}

If I press std-key 1 no output on console ( it seems shortcut action as
used is cauth before key-pressed event sent ).

After press key 1 from nummeric-keypad: pb1->enimateClick() is called (
no it's allso displayed correctly ) and on console: "Key pressed: 49"
displayed.

Maybe its better to work with key-events than shortcuts ( so far i've
seen only one shortcut is possible for each Button )

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/0

------------------------------------------------------------------------
On 2015-02-28T07:34:20+00:00 Harald-pollak wrote:

I thinkthis is a Problem with the QT-Shortcuts: this work-arround works
vor me:

in kcalc.cpp at the end of "void KCalculator::keyPressEvent(QKeyEvent
*e)":

        switch (e->key()) {
        case Qt::Key_0:
            // 0 is available in all number systems, so the Button will never 
be deactivated
            pb0->animateClick();
            break;
        case Qt::Key_1:
            // 1 is available in all number systems, so the Button will never 
be deactivated
            pb1->animateClick();
            break;
        case Qt::Key_2:
            if(pb2->isEnabled())
                pb2->animateClick();
            break;
        case Qt::Key_3:
            if(pb3->isEnabled())
                pb3->animateClick();
            break;
        case Qt::Key_4:
            if(pb4->isEnabled())
                pb4->animateClick();
            break;
        case Qt::Key_5:
            if(pb5->isEnabled())
                pb5->animateClick();
            break;
        case Qt::Key_6:
            if(pb6->isEnabled())
                pb6->animateClick();
            break;
        case Qt::Key_7:
            if(pb7->isEnabled())
                pb7->animateClick();
            break;
        case Qt::Key_8:
            if(pb8->isEnabled())
                pb8->animateClick();
            break;
        case Qt::Key_9:
            if(pb9->isEnabled())
                pb9->animateClick();
            break;
        case Qt::Key_Enter:
            if(pbEqual->isEnabled())
                pbEqual->animateClick();
            break;
        case Qt::Key_Equal:
            if(pbEqual->isEnabled())
                pbEqual->animateClick();
            break;
        case Qt::Key_Plus:
            if(pbPlus->isEnabled())
                pbPlus->animateClick();
            break;
        case Qt::Key_Minus:
            if(pbMinus->isEnabled())
                pbMinus->animateClick();
            break;
        case Qt::Key_Comma:
            if(pbPeriod->isEnabled())
                pbPeriod->animateClick();
            break;
        case Qt::Key_Asterisk:
            if(pbMultiplication->isEnabled())
                pbMultiplication->animateClick();
            break;
        case Qt::Key_Slash:
            if(pbDivision->isEnabled())
                pbDivision->animateClick();
            break;
        default:
            break;
        }

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/1

------------------------------------------------------------------------
On 2015-02-28T12:47:19+00:00 Cfeck wrote:

*** Bug 340846 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/2

------------------------------------------------------------------------
On 2015-04-21T15:58:52+00:00 Tomasz Przybył wrote:

*** This bug has been confirmed by popular vote. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/3

------------------------------------------------------------------------
On 2015-04-21T16:01:59+00:00 Tomasz Przybył wrote:

Distro: Arch Linux x64
Package details:
kcalc 15.04.0-1
plasma-desktop 5.2.2-3
plasma-framework 5.9.0-1
plasma-workspace 5.2.2-2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/4

------------------------------------------------------------------------
On 2015-04-27T18:24:19+00:00 Luis Lezcano Airaldi wrote:

I'm also facing this issue. The problem is that KConfig (the library
that manages keyboard shortcuts) is not reading Qt::Keypad_Modifier
which is set when pressing keypad keys.

https://bugs.kde.org/show_bug.cgi?id=346806

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/5

------------------------------------------------------------------------
On 2015-05-05T18:15:18+00:00 Vojtěch Erben wrote:

Same issue on Kubuntu 15.04 with KDE 5.3 (via kubuntu/backports ppa)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/6

------------------------------------------------------------------------
On 2015-05-06T18:50:53+00:00 Cfeck wrote:

*** Bug 347325 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/7

------------------------------------------------------------------------
On 2015-05-06T19:15:06+00:00 Cfeck wrote:

This is a regression in Qt5.

See patch and link to bug at https://codereview.qt-
project.org/#/c/95219/

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/8

------------------------------------------------------------------------
On 2015-05-09T09:39:48+00:00 Cfeck wrote:

*** Bug 347459 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/9

------------------------------------------------------------------------
On 2015-05-09T13:41:44+00:00 Rdieter-math wrote:

I can confirm the qt patch referenced in comment #8 seems to work as
advertised.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/10

------------------------------------------------------------------------
On 2015-05-12T13:40:35+00:00 Cfeck wrote:

*** Bug 347609 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/11

------------------------------------------------------------------------
On 2015-05-13T10:28:57+00:00 Cfeck wrote:

*** Bug 347648 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/12

------------------------------------------------------------------------
On 2015-05-14T15:12:02+00:00 Cfeck wrote:

*** Bug 347713 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/13

------------------------------------------------------------------------
On 2015-06-05T10:29:13+00:00 Cfeck wrote:

*** Bug 348695 has been marked as a duplicate of this bug. ***

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/14

------------------------------------------------------------------------
On 2015-06-05T17:42:54+00:00 Proteus5 wrote:

So what's the solution of this bug?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/15

------------------------------------------------------------------------
On 2015-06-05T17:45:22+00:00 Rdieter-math wrote:

See comment #8

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/16

------------------------------------------------------------------------
On 2015-06-05T18:19:32+00:00 Proteus5 wrote:

(In reply to Rex Dieter from comment #16)
> See comment #8

the explanation is a bit superficial, developer has to explain every
single step to the common user.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/17

------------------------------------------------------------------------
On 2015-06-05T18:20:43+00:00 Rdieter-math wrote:

In short, it's a Qt5 bug/issue, and the link in comment #8 is a proposed
fix (but not included in Qt5 sources yet, as of this moment)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/18

------------------------------------------------------------------------
On 2015-06-05T18:29:35+00:00 Proteus5 wrote:

(In reply to Rex Dieter from comment #18)
> In short, it's a Qt5 bug/issue, and the link in comment #8 is a proposed fix
> (but not included in Qt5 sources yet, as of this moment)

Ok thanks I'll wait for an update of kcalc itself which the bug will be
fixed.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/19

------------------------------------------------------------------------
On 2015-06-05T18:32:32+00:00 Rdieter-math wrote:

It's not a kcalc bug, so no kcalc update will fix this, but rather,
hopefully some future version of Qt5 will include a fix.

Feel free to bug/nag your distro into considering including the
candidate Qt5 fix (fedora does, for example)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/20

------------------------------------------------------------------------
On 2015-06-05T18:56:51+00:00 Proteus5 wrote:

(In reply to Rex Dieter from comment #20)
> It's not a kcalc bug, so no kcalc update will fix this, but rather,
> hopefully some future version of Qt5 will include a fix.
> 
> Feel free to bug/nag your distro into considering including the candidate
> Qt5 fix (fedora does, for example)

Ok thanks... by the way is chromium  played by qtwebengine planned to be
realized in the near future or some other KDE browser?

note: which=when in the previous comment.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/21

------------------------------------------------------------------------
On 2015-06-09T21:45:08+00:00 Proteus5 wrote:

EDIT: NEWS... I've installed again KUBUNTU 15.04 Before installing it
I've tested and kcalculator works by numlock activated it on the
keyboard. NOw or the problems concern with keyboard controller I changed
it enabling numlock boot activation, or problem concerns with PLASMA
upgrade I made before using kcalculator.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/22

------------------------------------------------------------------------
On 2015-07-13T09:54:21+00:00 Heart wrote:

I'm also suffering this bug now and I don't have Qt5 (it worked on
openSUSE 13.2 all the time. Must be something with latest KDE
updates...).

~  kde4-config --version
Qt: 4.8.6
KDE: 4.14.9
kde4-config: 1.0

I had kcalc v15.04.3-1.2 installed (from KDE:Applications repo)

i | kcalc             | Paket      | 15.04.3-1.2  | x86_64 |
KDE:Applications

So I tried downgrading kcalc package to latest version from openSUSE
13.2 OSS Update repo

zypper install --oldpackage kcalc-14.12.3-16.1.x86_64

and with that version the numkeys are working again!

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/23

------------------------------------------------------------------------
On 2015-07-28T10:30:41+00:00 Cfeck wrote:

Hermann, kcalc since version 15.04 uses Qt5, regardless of your Plasma
desktop version.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/24

------------------------------------------------------------------------
On 2015-09-25T01:52:07+00:00 Pelardonable wrote:

Please fix num-pad input.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/25

------------------------------------------------------------------------
On 2015-09-27T18:30:28+00:00 Cfeck wrote:

It is fixed in Qt (at least in the 5.6 branch, not sure if it was
backported to Qt 5.5.x).

Reply at:
https://bugs.launchpad.net/ubuntu/+source/kcalc/+bug/1503170/comments/26


** Changed in: kdeutils
       Status: Unknown => Won't Fix

** Changed in: kdeutils
   Importance: Unknown => Medium

** Bug watch added: KDE Bug Tracking System #346806
   https://bugs.kde.org/show_bug.cgi?id=346806

-- 
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kcalc in Ubuntu.
https://bugs.launchpad.net/bugs/1503170

Title:
  Numeric keypad not working in kcalc

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdeutils/+bug/1503170/+subscriptions

-- 
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs

Reply via email to