Bug 700881

Summary: [cutecw] in Recognition Training mode stopps accepting input when two keys are pressed at the same time
Product: [Fedora] Fedora Reporter: Jirka Daněk <juraad>
Component: cutecwAssignee: Wes Hardaker <wjhns174>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rawhideCC: wjhns174
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-24 23:54:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Jirka Daněk 2011-04-29 17:48:53 UTC
Description of problem:

When more than one key is pressed during Recognition Training mode, application stopps accepting aditional input.

Output of the program:
During practicing the letter 'k' for the third time, I hit letters 'k' and 'j' at the same time. It shouted 'KEY PRESSED EARLY' and and every next key was dismised with 'ignoring key press; too long and probably an interruption'

[jirka@private ~]$ cutecw --verbose
new morse2 
original buffer size:  0 
switch to: 0 
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
switch to: 2 
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
QLayout: Attempting to add QLayout "" to QWidget "", which already has a layout
setting up sequence buttons 
audio stopped 
playButton() 
--- Start next training key 
|keying:  'k' 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  1 ms ( 3600  WPM) 
WPM text:  "3600 " 
audio stopped 
--- Start next training key 
not good enough:  1 / 10 
   too low:  'k'  /  10  /  1 
randomizing:  32.9535  total:  190  min/max:  10 / 10 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  1 / 10 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  134 ms ( 26  WPM) 
WPM text:  "26 " 
audio stopped 
--- Start next training key 
not good enough:  2 / 10 
   too low:  'k'  /  20  /  2 
randomizing:  14.3683  total:  180  min/max:  20 / 20 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  2 / 10 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  118 ms ( 30  WPM) 
WPM text:  "30 " 
audio stopped 
--- Start next training key 
not good enough:  3 / 10 
   too low:  'k'  /  30  /  3 
randomizing:  51.467  total:  170  min/max:  30 / 30 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  3 / 10 
key pressed:  "j"   1   1 
Key pressed =  'j' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  134 ms ( 26  WPM) 
WPM text:  "26 " 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 0 , times= 0 
KEY PRESSED EARLY 
audio stopped 
--- Start next training key 
not good enough:  3 / 10 
   too low:  'k'  /  30  /  4 
randomizing:  48.4768  total:  170  min/max:  30 / 30 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  3 / 10 
--- Start next training key 
not good enough:  3 / 10 
   too low:  'k'  /  30  /  4 
randomizing:  119.563  total:  170  min/max:  30 / 30 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  3 / 10 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  70421392 ms ( 0  WPM) 
WPM text:  "0 " 
ignoring key press; too long and probably an interruption 
--- Start next training key 
not good enough:  3 / 10 
   too low:  'k'  /  30  /  4 
randomizing:  66.2467  total:  170  min/max:  30 / 30 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  3 / 10 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  70422640 ms ( 0  WPM) 
WPM text:  "0 " 
ignoring key press; too long and probably an interruption 
--- Start next training key 
not good enough:  3 / 10 
   too low:  'k'  /  30  /  4 
randomizing:  54.5125  total:  170  min/max:  30 / 30 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  3 / 10 
key pressed:  "k"   1   1 
Key pressed =  'k' , Queue of stored keys: keys= 1 , times= 1 
Training response: elapsed  70423904 ms ( 0  WPM) 
WPM text:  "0 " 
ignoring key press; too long and probably an interruption 
--- Start next training key 
not good enough:  3 / 10 
   too low:  'k'  /  30  /  4 
randomizing:  114.597  total:  170  min/max:  30 / 30 , count:  1 , magic:  200 
>keying:  'k' 
not good enough:  3 / 10 
saving! 

Version-Release number of selected component (if applicable):
CuteCW 1.0

How reproducible:
Easilly

Steps to Reproduce:

1. Run cutecw,
2. select Recognition Training on main screen.
3. Start it by clicking Play. Do some morse code pracicing
4. When you feel like it, "accidently" press two keys, like 'k' and 'j', when you are supposed to press only 'k'
  
Actual results:
5. from now on cutecw won't accept any input. 

First aid:
6. Clicking Pause and then Play will make it accept input again. Untill you hit more than one key again.

Comment 1 Wes Hardaker 2011-05-24 23:54:36 UTC
Will fix in the upstream.