Bug 68791 - Can't use the numeric keypad
Summary: Can't use the numeric keypad
Status: RESOLVED FIXED
Alias: None
Product: kcalc
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Klaus Niederkrüger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-22 14:02 UTC by Frederic Bages
Modified: 2004-10-27 00:27 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 Frederic Bages 2003-11-22 14:02:42 UTC
Version:            (using KDE KDE 3.1.93)
Compiler:          gcc (GCC) 3.2.3 20030422 (Gentoo Linux 1.4 3.2.3-r2, propolice) -march=athlon-xp -O3 -pipe
OS:          Linux

Typing the numeric keypad has not effect on kcalc display field.

If i use the normal number keys the display changes to append this key. With the numeric keypad nothing happen. I've tryed "num lock". I can reproduce this bug on 2 computers.

Step to reproduce :
Open Kcalc.
use the numeric keypad.

Result:
Nothing happen

Expected:
The keys hit should be appened to display.
Comment 1 Thiago Macieira 2003-11-22 14:49:07 UTC
Works fine here for me. Can you use the numeric keypad in another application, say Konqueror or Konsole?

Please run xev in Konsole, hit a key in the numeric keypad and paste the two events generated to this bug report (the KeyPress and the KeyRelease events).
Comment 2 Frederic Bages 2003-11-22 15:45:22 UTC
I can use the numeric keypad in Konsole, Konqueror and Kate.

the keypad numeric key "5" pressed in xev window fire the following events :

KeyPress event, serial 28, synthetic NO, window 0x3c00001,
    root 0x8d, subw 0x0, time 8411963, (48,88), root:(1146,874),
    state 0x10, keycode 84 (keysym 0xffb5, KP_5), same_screen YES,
    XLookupString gives 1 bytes:  "5"

KeyRelease event, serial 28, synthetic NO, window 0x3c00001,
    root 0x8d, subw 0x0, time 8412058, (48,88), root:(1146,874),
    state 0x10, keycode 84 (keysym 0xffb5, KP_5), same_screen YES,
    XLookupString gives 1 bytes:  "5"
Comment 3 Klaus Niederkrüger 2004-10-26 20:07:37 UTC
Does this bug still exist? Otherwise I would like to change it to FIXED.

Klaus
Comment 4 Frederic Bages 2004-10-26 20:15:26 UTC
I now use kcalc 1.6 on kde 3.3.1 and can't reproduce the problem. You can close this bug.
Comment 5 Klaus Niederkrüger 2004-10-27 00:27:28 UTC
Ok. Thanks.

  Klaus