Interacting with an application under a transparent layer

Abstract

Procedure that includes: Receiving a first handwriting input on a touch-sensitive screen of a device and associating the first handwriting input with an input region of a first user interface appearing on the touch-sensitive screen before changing focus to a second user interface, wherein the first user interface was in focus while receiving the associated user handwriting inputs and wherein the first user interface corresponds to a first unique identifier and the second user interface corresponds to a second unique identifier; Converting the first handwriting input into a first plurality of textually formatted data after changing the focus from the second user interface back to the first user interface; and Entering the textual formatted data into the input area of ​​the first user interface; the method further comprising: after changing the focus from the first user interface to the second user interface, searching a memory area for a stored association between the second identifier and a second handwriting input; and in response to the association being found during the search: Retrieving the second handwriting input from the storage area; and Displaying the retrieved second handwriting input in a handwriting input area of ​​the touch-sensitive screen.

Description

BACKGROUND

[0001] In ink-to-text conversion applications such as Lenovo WRITEit™ and Microsoft's Handwriting IME™, the handwriting ink already written by the user is not associated with a window or input field. Consequently, after system focus is changed by changing or closing the application window, the user's handwriting input is either lost or directed to another, incorrect application. To prevent this error, the user is currently required to actively convert the handwriting before changing focus to another window or application. This activity can reduce user productivity. Furthermore, some windows or applications, such as instant messaging applications, can "pop up" and gain focus without active user instruction or participation.When a focus change occurs through such pop-up windows, all the user's handwriting input is either lost or redirected to the wrong application, such as an instant messaging application.

[0002] US Pat. No. 7,461,348 B2 relates to the processing of computer input data (such as electronic ink data, voice input data, keyboard input data, etc.), including focus change data. User input data can be accepted before, during, and / or after a focus change event is triggered, and the input data is forwarded to areas of an application program that had focus at the time user input began. SUMMARY

[0003] It is an object of the present invention to enable improved processing of handwriting input on a touch-sensitive screen with multiple user interfaces.

[0004] This object is solved by the subject matter of main claim 1 and the independent claims 8 and 9, which determine the present invention.

[0005] Preferred embodiments of the present invention are the subject of the subclaims.

[0006] An approach is provided for associating handwriting on a touch-sensitive screen with application components. Before changing focus to a second user interface, a set of handwriting inputs is received on the touch-sensitive screen of a device. The received handwriting inputs are associated with an input area of ​​the first user interface appearing on the touch-sensitive screen, with the system focus being on the first user interface while the handwriting inputs are received. Thereafter, when the user changes focus from the second user interface back to the first user interface, the first set of handwriting inputs is retrieved, converted to a text format, and entered into the input area of ​​the first user interface.

[0007] The foregoing is a summary and thus necessarily contains simplifications, generalizations, and omissions of detail. Consequently, those skilled in the art will understand that the summary is merely illustrative and is not intended to be limiting in any way. Other aspects, features, and advantages of the invention will become apparent from the non-limiting detailed description provided below. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The disclosure may be better understood by reference to the accompanying drawings in which: Fig. 1 is a block diagram of a data processing system in which the methods described here can be implemented; Fig. 2 an extension of the Fig. 1 to illustrate that the methods described herein may be performed on a wide variety of information processing systems operating in a networked environment; Fig. Figure 3 is a diagram showing finger-based handwriting input being directed to the correct instruction using a handwriting management component; Fig. 4 is a flowchart showing steps performed by the handwriting management component; and Fig. 5 is a flowchart showing further steps performed by the handwriting management component in managing the handwriting window that receives the user's handwriting input. DETAILED DESCRIPTION

[0009] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used herein, the singular forms "a," "an," and "the" are intended to include plural forms, unless the context clearly dictates otherwise. It is further understood that the terms "comprises" and / or "comprising," as used herein, specify the presence of stated features, integers, steps, acts, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, acts, elements, components, and / or groups thereof.

[0010] The corresponding structures, materials, actions, and equivalents of all means or step-plus-function elements in the claims below are intended to include any structure, material, or action for performing the function in combination with other claimed elements as specifically claimed. The detailed description is intended to be illustrative but not exhaustive or to limit the invention to the form disclosed. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the invention. The embodiment was chosen and described in order to best explain the principles of the invention and the practical application in order to enable those skilled in the art to understand the invention in terms of various embodiments with various modifications as suited to the particular use contemplated.

[0011] As will be understood by those skilled in the art, aspects may be implemented as a system, method, or computer program product. Accordingly, aspects may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, microcode, etc.), or an embodiment combining software and hardware aspects, all of which may be generally referred to herein as a "circuit," "module," or "system." Furthermore, aspects of the present disclosure may take the form of a computer program product embodied in one or more computer-readable media having computer-readable program code embodied thereon.

[0012] Any combination of one or more computer-readable media may be used. The computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. A computer-readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or apparatus, or any suitable combination of the foregoing.More specific examples (non-exhaustive list) of the computer-readable storage medium include, but are not limited to: an electrical connection with one or more cables, a portable computer diskette, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by, or in connection with, an instruction execution system, apparatus, or device.

[0013] A computer-readable signal medium may include a propagated data signal having computer-readable program code, for example, in baseband or as part of a carrier wave. Such a propagated signal may take a variety of forms, such as, but not limited to, electromagnetic, optical, or any suitable combination thereof. A computer-readable signal medium may be any computer-readable medium, other than a computer-readable storage medium, that can transmit, carry, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. As used herein, a computer-readable storage medium does not include a computer-readable signal medium.

[0014] Computer program code for performing operations for aspects of the present disclosure may be written in any combination of one or more programming languages, for example, an object-oriented programming language such as Java, Smalltalk, C++, or the like, and conventional procedural programming languages ​​such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer over any type of network, for example, a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (e.g.,via an Internet service provider over the Internet).

[0015] Aspects of the present disclosure are described below with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, a specific computer, or other programmable data processing device to produce a machine, such that the instructions, executing via the processor of the computer or other programmable data processing device, provide means for implementing the functions / acts specified in the one or more flowchart and / or block diagram blocks.

[0016] These computer program instructions may also be stored in a computer-readable medium that can instruct a computer, other programmable data processing apparatus, or other devices to operate in a particular manner such that the instructions stored in the computer-readable medium produce an article of manufacture that includes instructions that implement the function / action specified in the one or more flowchart and / or block diagram blocks.

[0017] The computer program instructions may also be loaded into a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed in the computer, other programmable device, or other devices to produce a computer-implemented method, such that the instructions executing on the computer or other programmable device provide methods for implementing the functions / acts specified in the one or more flowchart and / or block diagram blocks.

[0018] The following detailed description generally follows the summary as provided above, further clarifying and expanding the definitions of the various aspects and embodiments as necessary. To this end, this detailed description first introduces a computing environment in Fig. 1 suitable for implementing the software and / or hardware techniques associated with the disclosure. A networked environment is Fig. 2 is illustrated as an extension of the basic computing environment to emphasize that modern computing techniques can be performed across multiple standalone devices.

[0019] Fig. 1 illustrates an information handling system 100, which is a simplified example of a computer system capable of performing the computational operations described herein. The information handling system 100 includes one or more processors 110 connected to a processor interface bus 112. The processor interface bus 112 connects the processors 110 to a northbridge 115, also known as a memory control node (MCH). The northbridge 115 connects to system memory 120 and provides a means by which one or more processors 110 can access the system memory. A graphics controller 125 also connects to the northbridge 115. In one embodiment, a PCI Express bus 118 connects the northbridge 115 to the graphics controller 125. The graphics controller 125 connects to a display device 130, such as a computer monitor.

[0020] The northbridge 115 and a southbridge 135 connect to each other using a bus 119. In one embodiment, the bus is a direct media interface (DMI) bus that transfers data at high speed in each direction between the northbridge 115 and the southbridge 135. In another embodiment, a peripheral component interconnect (PCI) bus connects the northbridge and the southbridge. The southbridge 135, also known as an I / O control node (ICH), is a chip that generally implements functions that operate at a slower speed than those provided by the northbridge. The southbridge 135 typically provides various buses used to connect various components. These buses include, for example, PCI and PCI Express buses, an ISA bus, a system management bus (SMBus or SMB), and / or a low pin count (LPC) bus.The LPC bus often connects to low-bandwidth devices such as Boot ROM 196 and legacy I / O devices (using a Super I / O chip). Legacy I / O devices (198) may include, for example, serial and parallel ports, a keyboard, a mouse, and / or a floppy disk controller. The LPC bus also connects Southbridge 135 to a Trusted Platform Module (TPM) 195. Other components often included in Southbridge 135 include a Direct Memory Access (DMA) controller, a Programmable Interrupt Controller (PIC), and a memory device controller that connects Southbridge 135 to a non-volatile memory device 185, such as a hard disk drive, using bus 184.

[0021] An ExpressCard 155 is a slot that connects hot-pluggable devices to the information processing system. The ExpressCard 155 supports both PCI Express and USB connectivity, as it connects to the Southbridge 135 using both the Universal Serial Bus (USB) and the PCI Express bus. The Southbridge 135 includes the USB controller 140, which provides USB connectivity for devices that connect via USB. These devices include a webcam (camera) 150, an infrared (IR) receiver 148, a keyboard and touchpad 144, and a Bluetooth device 146 that provides wireless personal area networks (PANs). The USB controller 140 also provides USB connectivity for other non-assignable USB-connected devices 142, such asa mouse, a removable non-volatile memory device 145, modems, network cards, ISDN connectors, fax machines, printers, USB hubs, and many other types of USB-connected devices. Although a removable non-volatile memory device 145 is shown as a USB-connected device, a non-volatile memory device 145 could be connected using a different interface, such as a Firewire interface, etc.

[0022] A wireless local area network (LAN) unit 175 connects to the southbridge 135 via the PCI or PCI Express bus 172. The LAN unit 175 typically implements one of the IEEE 802.11 standards of over-the-air modulation techniques, all of which use the same protocol to communicate wirelessly between the information handling system 100 and another computer system or device. An optical storage unit 190 connects to the southbridge 135 using a Serial ATA (SATA) bus 188. Serial ATA adapters and devices communicate over a high-speed serial connection. The Serial ATA bus also connects the southbridge 135 to other forms of storage devices, such as hard disk drives. Audio circuitry 160, such as a sound card, connects to the southbridge 135 via a bus 158.Audio circuitry 160 also provides functionality such as an audio line-in and optical digital audio-in port 162, an optical digital output and headphone port 164, internal speakers 166, and an internal microphone 168. An Ethernet controller 170 connects to the southbridge 135 using a bus such as the PCI or PCI Express bus. The Ethernet controller 170 connects the information handling system 100 to a computer network such as a local area network (LAN), the Internet, and other public and private computer networks.

[0023] Even if Fig. 1 shows an information processing system, the information processing system can take many forms. For example, the information processing system can take the form of a desktop, a server, a portable, a laptop, a notebook, or a computer or data processing system with another form factor. Furthermore, the information processing system can take other form factors such as a personal digital assistant (PDA), a gaming device, an automated teller machine (ATM), a portable telephone device, a communications device, or other devices that include a processor and memory.

[0024] The Trusted Platform Module (TPM 195), which is Fig. 1 and described herein to provide security functions is merely an example of a hardware security module. For this reason, the TPM described and claimed herein includes any type of HSM, including, but not limited to, hardware security devices that comply with the Trusted Computing Groups (TCG) standard and are entitled "Trusted Platform Module (TPM) Specification Version 1.2." The TPM is a hardware security subsystem that can be integrated into any number of information processing systems, such as the Fig. 2 outlined.

[0025] Fig. 2 represents an extension of the Fig. 1 to illustrate that the methods described herein can be performed on a wide variety of information processing systems operating in a networked environment. Types of information processing systems range from small mobile devices such as a mobile computer / cellular phone 210 to large mainframe systems such as a mainframe computer 270. Examples of the mobile computer 210 include personal digital assistants (PDAs), personal entertainment devices such as MP3 players, portable TVs, and CD players. Other examples of information processing systems include a pen or tablet computer 220, a laptop or notebook computer 230, a workstation 240, a personal computer system 250, and a server 260. Other types of information processing systems used in Fig. 2 are not individually shown, are represented by the information processing system 280. As shown, the various information processing systems may be networked together using a computer network 200. Computer network types that may be used to interconnect the various information processing systems include local area networks (LANs), wireless local area networks (WLANs), the Internet, the public telecommunications network (PSTN), other wireless networks, and any other network topology that may be used to interconnect the information processing systems. Many of the information processing systems include non-volatile data storage, such as hard disk drives and / or non-volatile memory. Some of the Fig. The information handling systems shown in Figure 2 depict separate non-volatile data storage devices (a server 260 uses a non-volatile data storage device 265, a mainframe 270 uses a non-volatile data storage device 275, and an information handling system 280 uses a non-volatile data storage device 285). The non-volatile data storage device may be a component external to the various information handling systems or internal to one of the information handling systems. Furthermore, the removable non-volatile storage device 145 may be shared by two or more information handling systems using various techniques, such as connecting the removable non-volatile storage device 145 to a USB port or other connector of the information handling systems.

[0026] The Fig. Figures 3-5 illustrate an approach that uses a handwriting management unit to track handwritten input provided by a user and the intended application of such handwritten input. The approach shown here associates handwritten input with the currently active application window or input field. This allows for appropriate actions to be taken when the window / field state changes, such as retaining handwritten input in memory, saving input to memory, converting input to text, and the like. Implementing this approach, the user need not worry about inadvertently losing their handwritten input, especially if significant handwriting has been entered by the user.

[0027] To associate a handwriting with a specific application window or field, a<Schlüssel, Wert> A model can be used to store the window identifier as the key and the handwriting data as the value. In one embodiment, a window identifier is used as the window handle. Handwriting data entered by the user is an abstract data object and could contain all information about the handwriting input, such as point data, format, structure, recognized result, timestamp, and so on.

[0028] The following outlines some of the scenarios where the association provided by this approach can be used. First, when the user opens a new window, before existing handwritten input is converted / processed, the input is first saved. Later, when a user switches back to the old window, the saved input is restored and reappears for use in the old window. Input can be associated with different text input fields, even within a single application window. Thus, when the user switches focus between input fields, the saved ink reappears accordingly. When the existing window is about to close, e.g.When a user clicks "Send" in an email application, if handwriting input is still present, it can be converted to the correct window based on knowledge of handwriting input associations before the window is actually closed. In another embodiment, the associated handwriting input can be re-associated with a different window or field. The associated handwriting input can be continuously updated, and the association can be removed at any time.

[0029] Fig. 3 is a diagram illustrating finger-based handwriting input being directed to the correct instruction using a handwriting management component. A touch-sensitive screen 300 is a display on an information handling system such as a laptop, tablet, smartphone, conventional computer system, or the like. A text field 310 is presented for a user to enter handwritten text using a user's hand 320, a stylus, or a similar implement. In one embodiment, the text field 310 appears when requested by the user, e.g., with a command, gesture, or other user input. The user enters handwriting, such as handwritten print, cursive, or other handwriting input, by pressing on the surface of the touch-sensitive screen in the area of ​​the text field 310.

[0030] In the example shown, two applications 330 and 360 are displayed on the touchscreen 300 display. Each of the applications is shown with two input areas or fields. Application 330 is shown with input areas 340 and 350, while application 360 is shown with input areas 370 and 375. As the name implies, handwriting management unit 385 manages the handwriting input provided by user 320. The handwriting management unit associates the focus area on the screen with the handwriting entered by the user. These associations are stored in storage area 390.

[0031] For example, if a field 340 of application 330 is a street address input field and the focus is on that field when the user provides a handwriting input of "Main Street 12," then handwriting management unit 385 associates the handwriting input of "Main Street 12" with the input field 340 of application 330. This association is stored in storage area 390. Suppose that before converting the address data input to text field 330, the user changes focus to the email field (field 375) of application 360. The address entered for street address field 340 would be stored in storage area 390, and the handwriting management unit would search handwriting data 390 to determine if a handwriting association already exists for the newly selected email field.If such an association does not yet exist, an empty text field 310 would be displayed and the user could enter the email address by hand (e.g., "maxmustermann@acme.com", etc.).

[0032] If the user selects the street address field (field 340 of application 330) again, a new association is saved—this time the email field (field 375 of application 360) is associated with the handwritten input (e.g., "johndoe@acme.com"). The handwriting management unit then searches the storage area 390 and locates the previously saved association for the street address fields (e.g., "12 Main Street"). The retrieved handwritten input is displayed in the text field 310, allowing the user to edit the handwritten data. If the user wishes to update the field, the user indicates this intent (e.g., through a command, gesture, etc., such as double-tapping the text field 310). This causes the handwritten input to be converted into a textual format, and the text is entered into the input area.In this example, the text "Main Street 12" would appear in the street address field 340 for the application 330. When the user selects the email field again, the handwritten input previously associated with the email field is retrieved from the storage area 390 and displayed in the text field 310.

[0033] Fig. Figure 4 is a flowchart showing steps performed by the handwriting management component. The processing of Fig. Figure 4 begins at 400 and shows the steps a process performs to perform the functions of the handwriting management units. In step 410, the process displays a new (empty) handwriting input session window. The handwriting input session window (text field 310) is displayed on the touch-sensitive screen 300. In step 420, the process retrieves the current identifier in focus, which is the currently selected item on the device. The current identifier could be a window identifier, a selected application and field, an identifier of a selected input area, etc.

[0034] In step 430, the process searches the storage area 390 for all currently stored associations for the retrieved identifier and retrieves the data from the handwriting data storage area 390. The process determines whether the current identifier is already in use for a handwriting session (decision 440). If the current identifier is already in use for a handwriting session, decision 440 branches to the "yes" branch to perform steps 450 and 460. In step 450, the process retrieves the handwriting input previously entered by the user for this identifier. In step 460, the process loads the retrieved handwriting input into a handwriting input session window (text field 310).

[0035] Referring again to decision 440, if the current identifier is not already used for a handwriting session, decision 440 branches to the "No" branch to initiate a new association. In step 470, the process allocates a new handwriting session and associates the user's handwriting input during that session with the retrieved current identifier.

[0036] In a predefined process 480, the handwriting management unit executes the handwriting window routine (see Fig. 5 and the corresponding text for processing details). The process determines whether the handwriting session is still active and has not yet been closed by the user (decision 490). If the handwriting session is still active, decision 490 branches to the "Yes" branch, which loops back to step 410 to repeat the process as described above. This loop continues until the handwriting session is no longer active, at which time decision 490 branches to the "No" branch and exits the loop. Processing of Fig. 4 then ends at 495.

[0037] Fig. Figure 5 is a flowchart showing further steps performed by the handwriting management component in managing the handwriting window that receives the user's handwriting input. Fig. Figure 5 begins at 500 and shows the steps a process performs to perform the functions of the handwriting window routine. In step 510, the user enters handwriting into a handwriting input session window (e.g., text field 310). The process determines whether the user continues handwriting or selects something else on the touch-sensitive screen (decision 520). If the user continues handwriting, decision 520 branches to the "Yes" branch, which continues looping back to step 510 so that the user can continue providing handwriting input. This continues until the user selects something else on the touch-sensitive screen display, at which time decision 520 branches to the "No" branch to process the user's action.

[0038] In step 530, the process stores the handwriting input data provided by the user in the handwriting input session window, along with the associated identifier. Step 530 stores the association (identifier and handwriting input associated with the identifier) ​​in the handwriting data storage area 390. The process determines whether a focus change has occurred on the device (decision 540), such as the user selecting on a different input field, as in Fig. 3. If a focus change has occurred, the decision 540 then branches to the “Yes” branch, with processing then returning to the calling routine (see Fig. 4) returns at 550. Note that processing returns without closing the input session window, so the input session window is still available to receive handwritten input associated with the newly selected application / field that is now in focus. Referring again to decision 540, decision 540 then branches to the "No" branch to continue processing the action if no focus change has occurred.

[0039] The process then determines whether the user has requested to convert handwriting input into textual data (decision 560). If the user has requested to convert handwriting input into textual data, decision 560 then branches to the "yes" branch, and the process then converts handwriting input by the user into text or another representation in step 570 and then sends the converted data to the identifier (e.g., an application field, etc.). After the handwriting has been converted, the process then removes (deletes) the handwriting input data and the associated identifier from the storage area 390 in step 580. In other words, step 580 deletes the association from memory.In one embodiment, instead of removing the handwriting input data from memory, step 580 performs a "shallow removal," during which the handwriting is visually removed so that the user no longer sees the ink, even when switching between windows. However, the shallow removal supports an "undo" operation, so that the user can reverse the conversion operation, and the ink will reappear. On the other hand, if the user has not requested to convert handwriting input to textual data, decision 560 then branches to the "no" branch, bypassing step 570.

[0040] A decision is made by the process as to whether the user wishes to delete the handwriting input currently associated with the current identifier (decision 575). If the user wishes to delete the handwriting input currently associated with the current identifier, decision 575 then branches to the "yes" branch to delete the handwriting data in step 580 (or performs "shallow removal," as described above). On the other hand, if the user does not wish to delete the handwriting input currently associated with the current identifier, decision 575 then branches to the "no" branch, bypassing step 580.

[0041] In step 590, the process closes the handwriting input session window. The processing of Fig. 5 then returns to the calling routine (see Fig. 4) back at 595.

[0042] Although particular embodiments have been shown and described, it will be apparent to those skilled in the art that changes and modifications may be made based on the teachings herein without departing from this disclosure and its broader aspects.

Claims

[1] Procedure which includes: Receiving a first handwriting input on a touch-sensitive screen of a device and associating the first handwriting input with an input region of a first user interface appearing on the touch-sensitive screen before changing focus to a second user interface, wherein the first user interface was in focus while receiving the associated user handwriting inputs and wherein the first user interface corresponds to a first unique identifier and the second user interface corresponds to a second unique identifier; Converting the first handwriting input into a first plurality of textually formatted data after changing the focus from the second user interface back to the first user interface; and Entering the textual formatted data into the input area of ​​the first user interface; the method further comprising: after changing the focus from the first user interface to the second user interface, searching a memory area for a stored association between the second identifier and a second handwriting input; and in response to the association being found during the search: Retrieving the second handwriting input from the storage area; and Displaying the retrieved second handwriting input in a handwriting input area of ​​the touch-sensitive screen. [2] The method of claim 1, further comprising: Removing an indication of the first handwriting input from the touch-sensitive screen in response to changing focus to the second user interface; and redisplaying the first handwriting input on the touch-sensitive screen before converting the first handwriting input into the plurality of textual formatted data after changing focus from the second user interface back to the first user interface. [3] The method of claim 1, further comprising: Receiving another second handwriting input on the touch-sensitive screen while the focus is on the second user interface; and Associating the further second handwriting input with the second user interface that appears on the touch-sensitive screen. [4] The method of claim 3, further comprising: in response to the fact that the association was not found in the search: Associating the second identifier and the second handwriting input, which is currently empty; and Display the empty second handwriting input in the handwriting input area of ​​the touchscreen. [5] The method of claim 4, further comprising: Receiving one or more handwriting inputs from the user via the handwriting input area; and Adding the one or more handwriting inputs received from the user to the second handwriting input associated with the second user interface in the storage area. [6] The method of claim 1, further comprising: in response to the association being found during the search, furthermore: Receiving a conversion request from the user; Converting the second handwriting input into a second plurality of textually formatted data; and Entering the second plurality of textually formatted data into an input area of ​​the second user interface. [7] The method of claim 6, further comprising: Deleting the second handwriting input from the storage area in response to converting the second handwriting input. [8] Information processing system comprising: one or more processors; a touch-sensitive screen accessible by at least one of the processors; a memory connected to at least one of the processors; and a set of instructions stored in memory and executed by at least one of the processors for performing a method according to any one of claims 1 to 7. [9] Computer program product comprising: a computer-readable storage medium comprising a set of computer instructions, the computer instructions being operable to carry out a method according to any one of claims 1 to 7.

Images