Browse Prior Art Database

Preventing Unexpected Push on Touch Panel

IP.com Disclosure Number: IPCOM000015563D
Original Publication Date: 2002-Feb-20
Included in the Prior Art Database: 2003-Jun-20
Document File: 2 page(s) / 74K

Publishing Venue

IBM

Abstract

Disclosed is a method to prevent unexpected push on touch panel. Fig. 1 shows the up/down state when the chattering occurs during a user's one push. In this case, two pushes are handled, though the user intended one push. That is, the second push is unexpected one. The duration of up state by the chattering ((1) in Fig. 1) is generally shorter than the duration of up state ((2) in Fig. 2) between double click. So, in case that a program receives a down event, if the duration of up state is shorter than a given time, the program can ignore the down event and the following up event.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 68% of the total text.

Page 1 of 2

Preventing Unexpected Push on Touch Panel

Disclosed is a method to prevent unexpected push on touch panel. Fig. 1 shows the up/down state when the chattering occurs during a user's one push. In this case, two pushes are handled, though the user intended one push. That is, the second push is unexpected one. The duration of up state by the chattering ((1) in Fig. 1) is generally shorter than the duration of up state ((2) in Fig. 2) between double click. So, in case that a program receives a down event, if the duration of up state is shorter than a given time, the program can ignore the down event and the following up event.

The duration of push (one relatively long click with chatering)

 Up status Down status

 Up status Down status

The duration of push (in case of double click)

The duration of up state The duratiby chataring ---- (1)on of up state between 2 clicks --- (2)

Fig. 1. Chataring

Fig. 2. Non Chataring (Double Click Case)

The redundant down and up events can be ignored as follows,

1. When a program receives down event, it processes the event only if the duration between preceding up event

and this down event is longer than the given time (e.g. 80 msec).
2. When a program receives up event, it processes the event only if the last processed event is the down event.

Fig. 3 shows the events which are processed or ignored by this method.

* The first down event (A) is processed because the duration between preceding up event (not shown in Fig. 3)

and this down even...