using the numeric keypad with the 'repeat' function causes incorrect tags

Bug #834951 reported by bell@archive.org
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Scribe2
New
Undecided
danh

Bug Description

1. Set the repeat cycle to 4 or 5 seconds in Scriblio.
2. Click 'Repeat'.
3. Begin image capture.
4. Quickly press the '5' or '6' numerical key twice for 'chapter'.

In a lot of cases, 'blank tissue' will appear instead of 'chapter'

summary: - using the numeriacal keypad with the 'repeat' function causes incorrect
+ using the numerical keypad with the 'repeat' function causes incorrect
tags
summary: - using the numerical keypad with the 'repeat' function causes incorrect
+ using the numeric keypad with the 'repeat' function causes incorrect
tags
danh (danh-archive)
Changed in scribe2:
assignee: nobody → danh (danh-archive)
Revision history for this message
danh (danh-archive) wrote :

Note that group3 has page types Appendix, Chapter, Subchapter, and Blank Tissue.

(See: petabox/www/sf/includes/scribe_keys.xml in the tree, or /var/www/includes/scribe_keys.xml on the scribes.)

So it sounds like 4 key presses are getting in before the page turn goes into effect (a sort of race condition).

Solution might be to rearrange the order of group 3 (as Jesse suggested in email) so that Chapter is first instead of second.

Revision history for this message
Jude Coelho (judec) wrote :

If you hold down the key on the keypad, does it count as multiple presses? If so, can we limit that in some way?

Revision history for this message
danh (danh-archive) wrote : Re: [Bug 834951] Re: using the numeric keypad with the 'repeat' function causes incorrect tags

Jude Coelho wrote:
> If you hold down the key on the keypad, does it count as multiple
> presses? If so, can we limit that in some way?
>

Hi Jude,

We can limit it --- and in fact, we already do, because the
000 key produces three events.

But this is a little tricky to do, because somebody could
just be typing very fast.

The device seems to emit an keycode of 144 both before
and after each actual press, so we might do a more sophisticated
key detection. (But we'd absolutely have to verify that.)

It might also be a good idea to try out a different device
so we can get some feel for what the scanners might be
most comfortable with. (And these devices might behave
differently as well.)

dan

Revision history for this message
danh (danh-archive) wrote :

Jesse --- would like some more status on this. (Is it still an issue, are there workarounds, what would you like done.)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.