Identifying input interruption

A computer detects user input within an input destination and determines whether the user input is continuous. If the user input is determined continuous, then the computer determines whether the input destination receiving the continuous user input has been changed during the receipt of the continuous user input. If the computer determines that the input destination has been changed during receipt of the continuous user input, the computer stores the portion of user input entered after the input destination had been changed in a temporary input buffer. The computer then presents the stored user input to a user and prompts a user selection of the appropriate input destination corresponding to the portion of stored user input.

TECHNICAL FIELD

The present invention relates generally to user input, and more particularly to identifying unwanted user input interruptions.

BACKGROUND

Computers are used for many tasks today. Those tasks often require a user input, such as data entry or operational instructions, entered into a fields known as input destinations. In order to enter user input into one of said input destinations, a user must select the window containing the input destination as the focus, or foreground, window. Sometimes during user input into an input destination, however, focus is diverted from the input destination by, for example, accidentally selecting the desktop or a background window assuming the foreground focus. Situations where a background window assumes the focus, and user input, of an input destination include a background window prompting an error dialogue window, alerting a user that a process is complete, displaying the opening of a new application (or instance thereof), displaying the receipt of new data/information, or prompting required user input/output. When a new input destination assumes the focus of the original input destination, the current user input, whether it be clicking, typing, scrolling, etc., is entered into the new input destination rather than the original input destination, often causing an undesirable result.

SUMMARY

Embodiments of the present invention disclose a method, system, and computer program product for identifying input interruption. A computer detects user input within an input destination and determines whether the user input is continuous. If the user input is determined continuous, then the computer determines whether the input destination receiving the continuous user input has been changed during the receipt of the continuous user input. If the computer determines that the input destination has been changed during receipt of the continuous user input, the computer stores the portion of user input entered after the input destination had been changed in a temporary input buffer. The computer then presents the stored user input to a user and prompts a user selection of the appropriate input destination corresponding to the portion of stored user input.

DETAILED DESCRIPTION

FIG. 1illustrates an input interrupt system100, in accordance with an embodiment of the invention. In the example embodiment, input interrupt system100includes network108, computing device110, and computing device120.

In the example embodiment, network108may be the Internet, representing a worldwide collection of networks and gateways to support communications between devices connected to the Internet. Network108may include, for example, wired, wireless or fiber optic connections. In other embodiments, network108may be implemented as an intranet, a local area network (LAN), or a wide area network (WAN). In general, network108can be any combination of connections and protocols that will support communications between computing device110and computing device120.

In the example embodiment, computing device120may be a laptop computer, a notebook, tablet computer, netbook computer, personal computer (PC), a desktop computer, a personal digital assistant (PDA), a smart phone, a thin client, or any other electronic device or computing system capable of receiving and sending data to and from other computing devices. While computing device120is shown as a single device, in other embodiments, computing device120may be comprised of a cluster or plurality of computing devices, working together or working separately. Computing device120is described in more detail with reference toFIG. 3.

In the example embodiment, computing device110includes application112application114, and input interrupt program116. In the example embodiment, computing device110may be a laptop computer, a notebook, tablet computer, netbook computer, personal computer (PC), a desktop computer, a personal digital assistant (PDA), a smart phone, a thin client, or any other electronic device or computing system capable of receiving and sending data to and from other computing devices. While computing device110is shown as a single device, in other embodiments, computing device110may be comprised of a cluster or plurality of computing devices, working together or working separately. Computing device110is described in more detail with reference toFIG. 3.

In the example embodiment, application112is a program application on computing device110which is designed to perform a group of coordinated functions, tasks, or activities, such as a web browsing application or anti-virus application. In the example embodiment, application112operates in a window and contains one or more input destinations capable of receiving user input. Furthermore, multiple instances of application112may be opened in multiple windows, each containing one or more input destinations. In situations where multiple windows are open (corresponding to multiple applications or a single application), one window is considered the foreground, or active, window while any other open windows are considered background, or inactive, windows. Although inactive windows are still operational, the active window is the only window capable of receiving user input within corresponding input destination(s). Similarly, when multiple input destinations are present within an active window, the input destination receiving user input is considered the active input destination while others are considered inactive input destinations.

In the example embodiment, application114is a program application on computing device110which is designed to perform a group of coordinated functions, tasks, or activities, such as a web browsing application or anti-virus application. In the example embodiment, application114operates in a window and contains one or more input destinations capable of receiving user input. Furthermore, multiple instances of application114may be opened in multiple windows, each containing one or more input destinations. In situations where multiple windows are open (corresponding to multiple applications or a single application), one window is considered the foreground, or active, window while any other open windows are considered background, or inactive, windows. Although inactive windows are still operational, the active window is the only window capable of receiving user input within corresponding input destination(s). Similarly, when multiple input destinations are present within an active window, the input destination receiving user input is considered the active input destination while others are considered inactive input destinations.

Input interrupt program116is a computer program capable of detecting the receipt of a user input and determining whether the user input is continuous. Input interrupt program116is additionally capable of determining whether the original input destination receiving the continuous user input has been replaced by a new input destination and, if so, storing the remainder of the continuous user input into a temporary input buffer. Input interrupt program116is further capable of implementing the stored input into the original or new input destination based on a user selection.

FIG. 2is a flowchart depicting the operation of input interrupt program116in identifying and resolving undesired user input entries that result from unexpectedly changing input destinations.

Input interrupt program116detects the receipt of a user input within an input destination by communicating with the operating system of computing device110. For example, input interrupt program116may detect the receipt of inputs such as mouse, microphone, touchscreen, keyboard, etc., and also inputs received from applications (such as popups or notifications) running on computing device110(step202). Such user inputs include typing (or key events), clicking (click events), scrolling, highlighting, speaking, gesturing, touching the screen, and other forms of communication directing computing device110. User inputs are entered within fields known as input destinations and one or more input destinations may be contained within the windows of application112and application114. Input destinations are fields capable of receiving user input and include text fields, dropdown menus, dials, radial buttons, scales, calendars, and buttons/button bars. In the example embodiment, user input can only be entered into one input destination at a time and, therefore, a selected input destination is known as the active input destination while other input destinations are known as inactive input destinations. In the example embodiment, input interrupt program116establishes a first input destination as the input destination to first receive user input, such as a click event or key event. For example, if a user would like to search for apple pie recipes in a web browsing application, application112, then the user selects a search bar input destination (making it active) within a window of the web browser and types “apple pie recipes”. Following the user selection of the search bar, the search bar input destination is considered both active and the first input destination. Note, however, that while an alternative input destination may become the active input destination, the input destination corresponding to the search bar will remain the first input destination until input interrupt program116stops receiving continuous user input.

Input interrupt program116determines whether the user input is continuous by communicating with the operating system of computing device110(decision204). In the example embodiment, if an input is continuous during a switch in input destinations, this may suggest that not only was the user interrupted, but also that the user did not intend to switch input destinations at that time and, thus, invoke remedial measures to match the appropriate input with the appropriate input destination. In the example embodiment, input interrupt program116determines whether input is continuous using a two-prong test, however, in other embodiments, determining whether an input is continuous may be performed alternatively. In the example embodiment, the first prong of the two-prong test determines whether events making up the user input (key events, click events, scroll events, etc.) occur within a specified time period of each other. Generally speaking, events in close temporal proximity to one another suggest that the user is mid-thought and input was intended to be uninterrupted. Furthermore, brief time periods between events is additionally indicative of a lack of opportunity to manually switch input destinations. While the time period may be configured by the user for each individual application and/or input destination, the default threshold time period between events is 500 milliseconds. Continuing the example above where the user is searching for apple pie recipes in the first (and active) input destination of application112(a web browser), if the time periods between the keystrokes of “apple pie recipes” range from 250 milliseconds to 400 milliseconds, then the user input passes the first prong of the continuousness test because the time periods between key events do not exceed 500 milliseconds. Conversely, temporal gaps between events suggest that the user may have paused and consciously contemplated switching input destinations before the input destination was changed. Additionally, pauses between events are indications that the user had the opportunity to manually switch input destinations. Continuing the example above, if the user typed the characters comprising the words “apple pie” with time periods of 250 milliseconds to 400 milliseconds between each character but pauses for 800 milliseconds between the characters in the word “recipes”, then the input “apple pie” passes the first prong of the continuousness test while the input of “recipes” does not pass the first prong of the continuousness test.

Passing prong one of the two-prong test prompts the second prong of the two-prong test in which input interrupt program116communicates with the operating system of computing device110to determine whether the coordinate positions of a mouse pointer (or alternative inputs) are within a threshold distance of the coordinates of the first input destination. Generally speaking, greater proximity of the mouse pointer to the input destination coordinates suggest that the user had the intent to stay within the current input destination. Additionally, if the mouse pointer (or alternative inputs) never leaves the area of the input destination, it is unlikely that the user intended to switch to different input destination. While the threshold distance may be set by the user for each individual application and/or input destination, the default threshold distance is 200 coordinate units in any direction. Continuing the example above with the user searching for apple pie recipes in the first and active input destination of application114, if the coordinates of the mouse location remain 150 coordinate units above the search bar during the user input, then the user input passes the second prong of the two prong test and the input is considered continuous. Conversely, lesser proximity between the coordinates of an input destination and the coordinates of the mouse pointer suggests that it may have been the intention of the user to exit the input destination. Continuing the example where a user is searching apple pie recipes in a first and active input destination application112window, if the mouse coordinates are 500 coordinate units to the right of the search bar, then the user input fails the second prong of the two-prong test because the coordinates of the mouse were more than 200 characters away from the coordinates of the search bar (first input destination). In further embodiments, the second prong of the two-prong test may be administered alternatively, such as determining whether the mouse (or alternative inputs) have moved a threshold distance during the receipt of the continuous user input. For example, if, during the receipt of continuous user input, the mouse pointer moves more than 300 coordinate units in any direction (regardless of input destination coordinate positions), then the user input fails the second prong of the two-prong test. While in the example embodiment the user input must pass both prongs of the two-prong test, in other embodiments, the user input may only have to pass a single prong of the two-prong test.

If input interrupt program116determines that the user input is not continuous (decision204“NO” branch), then input interrupt program116continues to detect user input within an active input destination (step202).

If input interrupt program116determines that the user input is continuous (decision204“YES” branch), then input interrupt program116communicates with the operating system and program applications of computing device110to determine whether the first input destination has become inactive during the receipt of a continuous user input (decisions206). In the example embodiment, an active input destination may be made inactive when a user accidentally clicks outside of the input destination/corresponding window or in situations where an inactive input destination/window requires user attention. Such situations where an inactive input destination/window require user attention include notification windows, such as prompting an error dialogue window, alerting the user that a process is complete, opening of new applications (or instances thereof), receipt of new data/information, or required user input/output (for example, overwrite duplicate file or save duplicate). Input interrupt program116determines whether the first input destination has become inactive by establishing a first input destination upon receipt of user input in step202and communicating with the operating system to determine whether the first input destination has become an inactive due to, for example, another window becoming the foreground (active) window. Continuing the example above, if a second input destination corresponding to application114becomes active while the user is entering a continuous input of “apple pie recipes” into the first input destination, then input interrupt program116determines that the first input destination has become inactive during the continuous input. Similarly, if, during the continuous entry of “apple pie recipes” into the first input destination, the user accidentally clicks the desktop, then input interrupt program116communicates with the operating system of computing device110to determine that the first input destination which was previously active has become inactive during a continuous user input.

If input interrupt program116determines that the active input destination has not become inactive during the continuous input (decision206“NO” branch), then input interrupt program116continues to detect user input within an active input destination (step202).

If input interrupt program116determines that the first input destination has become inactive during receipt of a continuous input (decision206“YES” branch), then input interrupt program116stores the remainder of the user input following the first input destination becoming inactive in a temporary input buffer (step208). In the example embodiment, the temporary input buffer stores the remainder of the user input (including key events, click events, etc.) after determining that the first input destination is no longer active. Furthermore, in the example embodiment, events stored in the temporary input buffer are not applied to the second (now active) input destination. Continuing the example above, if the user input (apple pie recipes) is considered continuous and the first input destination (corresponding to application112) is replaced by a second input destination (corresponding to application114window) after the letter “r” in recipes is input to the first input destination, then “apple pie r” remains in the first input destination while input interrupt program stores “ecipes” in the temporary input buffer (“ecipes” is not entered into the second input destination). Similarly, if input interrupt program determines that click or scroll events are continuous during an input destination activity change, then input interrupt program116stores the click and scroll events following the first input destination becoming inactive in the temporary input buffer without applying them to the second input destination.

Input interrupt program116presents a user interface to the user prompting selection of the appropriate input destination for the input stored in the temporary input buffer (step210). In the example embodiment, input interrupt program116displays the user input stored in the temporary input buffer as well as selectable options corresponding to the first input destination and the second input destination, if applicable. Continuing the example above where the first input destination is replaced (or made inactive) by the second input destination, if the temporary input buffer contains “ecipes”, then input interrupt program116displays a user interface containing the user input “ecipes” and options to implement the input into the first input destination or second input destination.

Computing device110may include one or more processors302, one or more computer-readable RAMs304, one or more computer-readable ROMs306, one or more computer readable storage media308, device drivers312, read/write drive or interface314, network adapter or interface316, all interconnected over a communications fabric318. Communications fabric318may be implemented with any architecture designed for passing data and/or control information between processors (such as microprocessors, communications and network processors, etc.), system memory, peripheral devices, and any other hardware components within a system.

One or more operating systems310, and one or more application programs311, for example, input interrupt116, are stored on one or more of the computer readable storage media308for execution by one or more of the processors302via one or more of the respective RAMs304(which typically include cache memory). In the illustrated embodiment, each of the computer readable storage media308may be a magnetic disk storage device of an internal hard drive, CD-ROM, DVD, memory stick, magnetic tape, magnetic disk, optical disk, a semiconductor storage device such as RAM, ROM, EPROM, flash memory or any other computer-readable tangible storage device that can store a computer program and digital information.

Computing device110may also include a R/W drive or interface314to read from and write to one or more portable computer readable storage media326. Application programs311on computing device110may be stored on one or more of the portable computer readable storage media326, read via the respective R/W drive or interface314and loaded into the respective computer readable storage media308.

Computing device110may also include a network adapter or interface316, such as a TCP/IP adapter card or wireless communication adapter (such as a 4G wireless communication adapter using OFDMA technology). Application programs311on computing device110may be downloaded to the computing device from an external computer or external storage device via a network (for example, the Internet, a local area network or other wide area network or wireless network) and network adapter or interface316. From the network adapter or interface316, the programs may be loaded onto computer readable storage media308. The network may comprise copper wires, optical fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers.

Computing device110may also include a display screen320, a keyboard or keypad322, and a computer mouse or touchpad324. Device drivers312interface to display screen320for imaging, to keyboard or keypad322, to computer mouse or touchpad324, and/or to display screen320for pressure sensing of alphanumeric character entry and user selections. The device drivers312, R/W drive or interface314and network adapter or interface316may comprise hardware and software (stored on computer readable storage media308and/or ROM306).