JP2011054213A - Information processor and control method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To make a user certainly recognize whether or not a mode is a hovering mode. <P>SOLUTION: This information processor includes: a first control means displaying a first image on a display screen of a display device; an operation reception means receiving a touch operation to the display screen; a second control means displaying information about the first image on the display screen when the operation reception means receives a touch operation to the first image while receiving the touch operation to a first area positioned in a partial area of the display screen; and a third control means starting an application corresponding to the first image when the operation reception means receives the touch operation to the first image while not receiving the touch operation to the first area. <P>COPYRIGHT: (C)2011,JPO&INPIT

Description

  The present invention relates to an information processing apparatus and a control method for switching between a hovering mode and a normal mode.

  In recent years, notebook personal computers including a touch panel including a display device and a position detection device provided on a display screen of the display device have been sold.

  As the position detection device, there are methods such as a resistance film method and an electromagnetic induction method. Generally, an event indicating a position and an event indicating that a mouse button is pressed are passed to an application program that controls a window displayed at a position detected by the position detection device.

  However, since it is inconvenient if the application program recognizes that the mouse button is always pressed, a mode called a hovering mode may be provided. In the hovering mode, only the event indicating the position is passed to the application program.

  Patent Document 1 discloses that a hovering icon for setting a hovering mode is provided on a display screen, and when the hovering icon is touched in a normal mode, the hovering mode is set until the next touching of the hovering icon.

JP 2000-122808 A (paragraph number [0022])

  In the technique disclosed in the above-described document, the hovering mode and the normal mode are switched by touching the hovering icon. Therefore, if the user leaves the computer for a while, the user may not know whether the current mode is the hovering mode or the normal mode.

  An object of the present invention is to provide an information processing apparatus and a control method that allow a user to reliably recognize whether or not the hovering mode is set.

  An information processing apparatus according to an example of the present invention includes: a first control unit that displays a first image on a display screen of a display device; an operation reception unit that receives a touch operation on the display screen; and the operation reception unit includes the display Second control for displaying information about the first image on the display screen when the touch operation is performed on the first image while the touch operation is performed on the first region located in a partial region of the screen. And a third control unit that activates an application corresponding to the first image when the operation accepting unit receives a touch operation on the first image while not receiving a touch operation on the first region. Is provided.

  According to the present invention, the user can surely recognize whether the hovering mode or the normal mode is set.

1 is a block diagram showing a system configuration of an information processing apparatus according to a first embodiment. The figure which shows the state which is pressing the other location with the finger in the state set to the hovering mode by pressing the inside of the hovering mode area with the finger. The figure which shows the structure for not handing over the button down event to the application program by which the mouse cursor is drawn, when switching to the hovering mode / normal mode concerning 1st Embodiment, and setting the hovering mode. The flowchart which shows the procedure which the mode setting module for setting to the hovering mode and normal mode concerning 1st Embodiment processes. 6 is a flowchart showing a processing procedure of an event handle module when a mouse event according to the first embodiment is passed. The figure which shows the state which is displaying the tool tip by setting to hovering mode. The figure which shows the state in which the launcher program is displaying the balloon by setting to hovering mode. The figure which shows the state which is performing the mouse | mouth gesture by setting to hovering mode. The figure which shows the state which has pressed the display screen with the finger | toe in the state which the user pressed the button and set to the hovering mode. The figure which shows the structure for not handing over a button down event to the application program by which the mouse cursor is drawn, when switching to the hovering mode / normal mode concerning 2nd Embodiment, and setting the hovering mode. The flowchart which shows the procedure which the mode setting module for setting to the hovering mode and normal mode concerning 2nd Embodiment processes. 9 is a flowchart showing a processing procedure of an event handle module when a mouse event according to the second embodiment is passed.

  Embodiments of the present invention will be described below with reference to the drawings.

(First embodiment)
First, the configuration of an information processing apparatus according to an embodiment of the present invention will be described with reference to FIG. This information processing apparatus is realized as a battery-driven portable notebook personal computer.

  Next, the system configuration of the computer will be described with reference to FIG.

  As shown in FIG. 1, the computer includes a display unit 12, a CPU 111, a north bridge 112, a main memory 113, a graphics controller 114, a south bridge 119, a BIOS-ROM 120, a hard disk drive 121, an embedded controller / keyboard controller IC 124. And a power controller 125 and the like.

  The CPU 111 is a processor provided for controlling the operation of the computer, and executes an operating system and various application programs loaded from the hard disk drive 121 to the main memory 113.

  The CPU 111 also executes a BIOS program stored in the BIOS-ROM 120. The BIOS program is a program for hardware control.

  The north bridge 112 is a bridge device that connects the local bus of the CPU 111 and the south bridge 119. The north bridge 112 also includes a memory controller that controls access to the main memory 113. The north bridge 112 also has a function of executing communication with the graphics controller 114 via an AGP bus or the like.

  The display unit 12 incorporates a display device including an LCD 17. A pressure-sensitive (resistive film type) touch sensor 18 is mounted on the image display surface of the LCD 17. The touch sensor 18 outputs a detection signal indicating a pressed position when the surface is pressed. The touch sensor 18 of the present embodiment can detect two pressed locations at the same time, and can output two detection signals indicating the detected pressed locations.

  The graphics controller 114 is a display controller that controls the LCD 17 used as a display monitor of the computer. The graphics controller 114 includes a video memory 114A, and generates a video signal that forms a display image to be displayed on the LCD 17 of the display unit 12 from display data written in the video memory 114A by the OS / application program.

  The south bridge 119 controls devices on the LPC bus. Further, the south bridge 119 includes an IDE controller for controlling the HDD 121. Furthermore, the south bridge 119 also has a function for controlling access to the BIOS-ROM 120. Further, the south bridge 119 has a USB controller 119A for controlling data transmission with a device that supports the USB standard. The touch sensor 18, which is a device that supports the USB standard, transmits data to the USB controller 119A in the south bridge 119.

  The embedded controller / keyboard controller IC 124 is a one-chip microcomputer in which an embedded controller for power management and a keyboard controller for controlling the keyboard 13 and the touch pad 16 are integrated. The embedded controller / keyboard controller IC 124 has a function of powering on / off the computer in accordance with the operation of the power button 14 by the user by operating in cooperation with the power supply controller 125.

  When the touch sensor 18 outputs a detection signal, the operating system issues a mouse event as an event related to the button operation of the pointing device. At this time, the mouse event issued by the operating system is a position event indicating the position of the mouse cursor and a button down event indicating that the mouse button is pressed.

  When an operation is performed with a normal mouse, a tooltip indicating supplementary information such as a file indicated by the icon is displayed when the pointer is over the icon of the explorer or the desktop.

  However, when the pointer is operated on the touch panel, the following inconvenience occurs. When a pointer is operated on the touch panel, a tool tip cannot be displayed because a button down event is always issued.

In this apparatus, it is possible to prevent such a problem from occurring. Hereinafter, a configuration for preventing the occurrence of inconvenience will be described.
As shown in FIG. 2, a hovering mode area RH, which is a virtual button, is set, for example, in the lower left corner area of the display. When the detection signal indicating that the inside of the hovering mode region RH is pressed with the finger F1 or the like is output from the touch sensor, the hovering mode is set. In the hovering mode, when a detection signal indicating that a region other than the hovering mode region RH is being pressed with the finger F2 or the like is output from the touch sensor, the mouse cursor draws an event related to the operation of the mouse button. The application program in which the mouse cursor is drawn is passed only to the event indicating the position of the mouse cursor without passing to the application program. When the area other than the hovering mode area RH is not pressed with the finger F2 or the like, the normal mode is set. In the normal mode, an application program in which the mouse cursor is drawn is passed as an event indicating the operation of the mouse button and the position of the mouse cursor.

  With reference to FIG. 3, a configuration for switching the hovering mode / normal mode and not passing the button down event to the application program in which the mouse cursor is drawn when the hovering mode is set will be described.

  As shown in FIG. 3, it comprises an operating system 201, a device driver 202, an event hook / handle module 210, and the like.

  The device driver 202 uses the same driver as the device driver of the normal touch sensor 18. Therefore, the device driver 202 acquires position information indicating the pressed location from the detection signal by the touch sensor 18. The device driver 202 passes the position information to the operating system 201. The operating system 201 performs processing for passing a mouse event including a position event and a button down event to an application program (desktop environment application 221 or launcher application 222) displayed at the position indicated by the position information. The desktop environment application 221 is a window control unit that displays the desktop screen as one of the windows on the display screen. The launcher application 222 is a window control means for displaying a window having a button for starting an application on the desktop screen.

  The event hook / handle module 210 includes a hook module 211, a mode setting module 212, an event handle module 213, and the like. The hook module 211 hooks the position event and the button down event output from the device driver 202. The mode setting module 212 switches between the hovering mode and the normal mode based on the position on the display screen indicated by the position event. The event handle module 213 passes the position event and the button down event to the original destination application program in the normal mode. The event handle module 213 passes only the position event to the application program that is the original destination in the hovering mode.

Next, a procedure performed by the mode setting module 212 for setting the hovering mode and the normal mode will be described with reference to the flowchart of FIG.
First, the hook module 211 hooks a position event and a button down event (step S10). The mode setting module 212 determines whether or not two mouse events have been hooked (step S11). If it is determined that the two mouse events are not hooked (No in step S11), the mode setting module 212 acquires position information indicating the position on the display screen from the position event of the mouse event (step S12). The mode setting module 212 determines whether or not the position information indicates the hovering mode area RH (step S13). When it is determined that the inside of the hovering mode region RH is indicated (Yes in step S13), the value of the flag 214 is set to True to set the hovering mode (step S14). Then, the mouse event is passed to the event handle module 213 (step S15). If it is determined in step S13 that the inside of the hovering mode region RH is not indicated (No in step S13), the mode setting module 212 sets the value of the flag 214 to False to set the normal mode (step S16). Then, the mouse event is passed to the event handle module 213 (step S17).

  If it is determined in step S11 that two mouse events have been hooked (Yes in step S11), position information indicating the position on the display screen from one of the two mouse events (hereinafter referred to as the first mouse event). Is acquired (step S22). The mode setting module 212 determines whether or not the position information indicates the hovering mode area RH (step S23). When it is determined that the inside of the hovering mode region RH is indicated (Yes in step S23), the value of the flag 214 is set to True to set the hovering mode (step S24). Then, the other event of the two mouse events (hereinafter referred to as a second mouse event) is passed to the event handle module 213 (step S25).

  If it is determined in step S23 that the inside of the hovering mode region RH is not indicated (No in step S23), position information indicating the position on the display screen is acquired from the second mouse event (step S32). The mode setting module 212 determines whether or not the position information indicates the hovering mode area RH (step S33). If it is determined that the hovering mode area RH is indicated (Yes in Step S33), the value of the flag 214 is set to True to set the hovering mode (Step S34). Then, the second mouse event is passed to the event handle module 213 (step S35).

  If it is determined in step S33 that the inside of the hovering mode region RH is not indicated (No in step S33), the mode setting module 212 sets the value of the flag 214 to False to set the normal mode (step S36). Then, the mouse event is passed to the event handle module 213 (step S37).

  The description of the processing procedure when the hook module 211 acquires a mouse event ends. By the above process, when the user is pressing inside the hovering mode area RH, the hovering mode can be set.

  The mode is set to the hovering mode when the user is pressing in the hovering mode region RH, and is set to the normal mode when the user is not pressing in the hovering mode region RH. Can be reliably identified.

Next, with reference to FIG. 5, the processing procedure of the event handle module 213 when a mouse event is passed will be described.
When a mouse event is passed, the event handle module 213 determines whether two mouse events have been passed (step S41). If it is determined that two mouse events have not been passed (No in step S41), the event handle module 213 refers to the value of the flag 214 and determines whether the hovering mode is set from the value of the flag 214 (True, False). Is determined (step S42). When it is determined that the hovering mode is set (Yes in step S42), the event handle module 213 deletes the button down event from the mouse event and leaves only the position event (step S43). Then, the mouse event from which the button down event has been deleted is delivered to the application program that is the original delivery destination of the mouse event (step S44).

  If it is determined in step S42 that the mode is not the hovering mode (No in step S42), the event handle module 213 passes the mouse event that is the original destination of the mouse event to the application program without changing the mouse event (step S42). S45). If it is determined in step S41 that two mouse events have been passed (Yes in step S41), the event handle module 213 passes each mouse event to the application program that is the original destination of each mouse event (step S45).

  With the above processing, a mouse event issued by a general-purpose device driver in the hovering mode can be changed to a mouse event in which the button down event is deleted.

When the hovering mode is set, there are the following advantages.
For example, as shown in FIG. 6, in the state where the hovering mode area RH on the display screen is pressed with the finger F1 to enter the hovering mode, the mouse cursor 302 is moved to the icon 301 on the desktop screen by pressing with the finger F2. Overlapping. Then, it becomes possible to display a tool tip 303 indicating the information of the file indicated by the icon 301.

  Further, as shown in FIG. 7, a button 402 in a window 401 displayed by the launcher program when pressed with the finger F2 in the hovering mode by pressing the hovering mode area RH on the display screen with the finger F1. The mouse cursor 403 is superimposed on the top. Then, information about the application program activated by the operation of the button 402 can be displayed on the balloon 404.

  In addition, as shown in FIG. 8, by moving the mouse cursor by pressing and moving with the finger F2 in the hovering mode by pressing the hovering mode area RH on the display screen with the finger F1. By adding the mouse gesture mode, you can perform mouse gestures by hovering. A line 502 displayed on the display screen is a movement locus of the mouse cursor 501.

  A touch screen such as a digitizer realizes hovering by using a dedicated pen. However, in this apparatus, the same operation as hovering with a pen can be performed with a finger. In addition, it is considered that a user who is accustomed to operating a mouse in Windows (registered trademark) feels troublesome when using a touch display whose main operation is “selection” by touch. If the same operation as a conventional mouse is realized by the hovering function, it is freed from the hassle.

(Second Embodiment)
Instead of pressing the hovering mode area RH on the display screen, as shown in FIG. 9, the user provided on the main body of the computer 10 presses a dedicated button 601 for setting the hovering mode with the finger F1. The hovering mode may be set by pressing the button. Note that the hovering mode may be set by pressing a specific key (for example, the Alt key) in the keyboard 13 instead of the mode setting button 601. In FIG. 9, the display screen of the computer 10 is pressed with the finger F2.

FIG. 10 shows the configuration of the event hook / handle module that is set to the hovering mode using the button 601.
A button 601 is a key for setting the hovering mode. When the user presses the button 601, the hovering mode is set. When the button 601 is not pressed, the normal mode is set.

  The operating system 201 uses the same driver as a normal key device driver.

  As shown in FIG. 10, the event hook / handle module 610 includes a mouse event hook module 611, a mouse event handle module 612, a key event hook module 613, a mode setting module 614, a flag 615, and the like.

  The mouse event hook module 611 hooks a mouse event issued to the application by the operating system 201. Similar to the event handle module 213 described with reference to FIG. 3, the mouse event handle module 612 deletes the button down event in the mouse event in the hovering mode, and sends the mouse event including the position event to the original issue destination. Pass to an application.

  The key event hook module 613 hooks a key event issued by the operating system 201 and passes it to the mode setting module 614. The mode setting module 614 sets the hovering mode by setting the value of the flag 615 to True when the passed key event indicates pressing of the button 601. The mode setting module 614 sets the normal mode by setting the value of the flag 615 to False when the delivered key event does not indicate that the button 601 has been pressed. The mode setting module 614 sets the normal mode by setting the value of the flag 615 to False when no key event is passed.

Next, a procedure of processing for setting the hovering mode and the normal mode will be described with reference to the flowchart of FIG.
First, the mode setting module 614 determines whether or not a key event has been passed from the key event hook module 613 (step S51). If it is determined that no key event has been passed (No in step S51), the value of the flag 615 is set to False to set the normal mode (step S54). If it is determined that a key event has been passed (Yes in step S51), the mode setting module 614 determines whether or not the key event is a key event indicating the pressing of the button 601 for setting the hovering mode (step S51). S52). If it is determined that the button 601 has been pressed (Yes in step S52), the value of the flag 615 is set to True and the hovering mode is set (step S53). When it is determined that the button 601 has not been pressed (No in Step S52), the value of the flag 615 is set to False to set the normal mode (Step S53).

  When the user presses the button 601, the hovering mode is set, and when the user does not press the button 601, the normal mode is set, so that the user is surely identified in which mode. Is possible.

Next, a processing procedure when the mouse event hook module 513 hooks a mouse event will be described with reference to the flowchart of FIG.
First, the mouse event hook module 513 hooks a mouse event (step S61). The mouse event hook module 513 passes the hooked mouse event to the mouse event handle module 612.

  The mouse event handle module 612 refers to the value of the flag 615 and determines whether or not the hovering mode is set based on the value of the flag 615 (True, False) (step S62). If it is determined that the hovering mode is set (Yes in step S62), the mouse event handle module 612 deletes the button down event from the mouse event and leaves only the position event (step S63). Then, the mouse event handle module 612 passes the mouse event from which the button down event has been deleted to the application program that is the original destination of the mouse event (step S64).

  When it is determined that the mode is not the hovering mode (No in step S62), the mouse event handle module 612 passes the mouse event that is the original destination of the mouse event to the application program without changing the mouse event (step S65). .

  With the above processing, a mouse event issued by a general-purpose device driver in the hovering mode can be changed to a mouse event in which the button down event is deleted.

  As described above, by setting the hovering mode when the pressing operation in the hovering mode area in the display screen or the pressing operation of the button 601 is performed, the user can set the current hovering mode and the normal mode. It is possible to reliably identify either.

  Note that the present invention is not limited to the above-described embodiment as it is, and can be embodied by modifying the constituent elements without departing from the scope of the invention in the implementation stage. Further, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the embodiment. For example, some components may be deleted from all the components shown in the embodiment. Furthermore, you may combine suitably the component covering different embodiment.

  DESCRIPTION OF SYMBOLS 12 ... Display unit, 17 ... LCD, 18 ... Touch sensor, 201 ... Operating system, 202 ... Device driver, 210 ... Handle module, 211 ... Hook module, 211 ... Hook module, 212 ... Mode setting module, 213 ... Event handle module , 214 ... Flag, 221 ... Desktop environment application, 222 ... Launcher application, RH ... Hovering mode area, 601 ... Button, 610 ... Handle module, 611 ... Mouse event hook module, 612 ... Mouse event handle module, 613 ... Key event hook Module, 613, key event hook module, 614, mode setting module, 614, mode setting module, 615, flag.

Claims (6)

First control means for displaying a first image on a display screen of a display device;
Operation accepting means for receiving a touch operation on the display screen;
When the operation accepting unit receives a touch operation on the first image while receiving a touch operation on the first region located in a partial region of the display screen, the information about the first image is A second control means for displaying on the display screen;
Information provided with third control means for activating an application corresponding to the first image when the operation accepting means receives a touch operation on the first image while not receiving a touch operation on the first area. Processing equipment.   The information processing apparatus according to claim 1, wherein the first control unit displays a button at a position of the first area of the display screen.   The information processing apparatus according to claim 1, wherein the first area is located at an end of the display screen.   The information processing apparatus according to claim 1, wherein the first area is located in a lower left part of the display screen. Display control means for displaying an image on the display screen of the display device;
Operation accepting means for receiving a touch operation on the display screen;
An information processing apparatus comprising: a switching unit that switches between a hovering mode and a normal mode according to whether or not the operation receiving unit has received a touch operation on a first region located in a partial region of the display screen. A control method in an information processing apparatus for displaying an image on a display device,
Displaying a first image on a display screen of the display device;
Displaying information about the first image when receiving a touch operation on the first image while receiving a touch operation on the first region located in a partial region of the display screen;
A control method comprising: activating an application corresponding to the first image when the touch operation is performed on the first image while the touch operation is not performed on the first region.

Images