JP5737082B2 - Pointer position correction method, pointer position correction program, and server apparatus - Google Patents

Description

  The present invention relates to a pointer position correction method and the like.

  In recent years, a thin client system has attracted attention from the viewpoint of strengthening security and reducing TCO (Total Cost of Ownership). The thin client system includes a server and a client connected to each other via a network. Then, the contents operated by the client are transferred to the server via the network, and the operation result is transferred from the server to the client and displayed on the client screen.

  The communication protocol between the server and the client of the syncline system is roughly classified into two types. The first is a command transfer method adopted in the Windows (registered trademark) standard remote desktop protocol (RDP). In the command transfer method, a drawing command for the desktop screen of the server is transferred to the client, and the drawing command is executed by the client that has received the drawing command to perform screen drawing. The second is a screen transfer method adopted in VNC (Virtual Network Computing) and the like. In the screen transfer method, the contents of the server desktop screen are transferred to the client as an image such as a bitmap or JPEG, and the transferred image is displayed on the client screen.

  When displaying a large number of objects such as CAD, the command transfer method increases the number of drawing commands in proportion to the number of objects and increases the operation delay. Therefore, in this case, the screen transfer method is more suitable than the command transfer method. However, in the screen transfer method, the drawing speed of the mouse cursor by the mouse operation is an important point that determines usability.

  As a mouse cursor drawing method, there are a server drawing method in a screen transfer method and a local echo method in a command transfer method. In the server drawing method, the contents of the mouse cursor drawn on the server desktop screen are sent to the client as they are, and the sent mouse cursor contents are drawn on the client screen. FIG. 23 is a diagram for explaining a server drawing method that is a drawing method of a mouse cursor. As shown in FIG. 23, the client transmits an input event to the server. Then, the server receives the transmitted input event, processes the received input event, and transmits the content of the processed mouse cursor as it is to the client. The client receives the content of the transmitted mouse cursor and displays the movement result of the mouse cursor on the screen based on the received content of the mouse cursor.

  On the other hand, the local echo method transmits an input event from the client to the server and draws a mouse cursor on the client side. FIG. 24 is a diagram for explaining a local echo method which is a drawing method of a mouse cursor. As shown in FIG. 24, the client transmits an input event to the server and draws the movement result of the mouse cursor on the screen. Therefore, the response performance of the mouse cursor is better in the local echo method that does not wait for the processing result of the input event than the server drawing method that transmits the processing result of the input event after transmitting from the client to the server.

  In addition, in the server drawing method in the screen transfer method, a technique for reducing the communication frequency associated with the movement of the mouse cursor is disclosed. In this technique, when the server generates display drawing data corresponding to an input event from the client to the server, a table is generated in which the cursor ID is associated with the area information of the object included in the drawing data. Then, the server transmits the created table to the client together with the drawing data. The client moves the cursor while drawing data corresponding to the input event is displayed. Then, the client determines from the table the cursor ID in the object area corresponding to the movement position of the cursor, and draws the shape of the cursor corresponding to the cursor ID at the moved cursor position.

JP 2010-2111724 A

  However, in the screen transfer method, if the drawing method of the mouse cursor is the local echo method, there is a problem that the client side cannot cope when the position and shape of the mouse cursor are automatically changed on the server. That is, the client side draws a mouse cursor at a position corresponding to the input event by itself and transmits the input event to the server. Accordingly, when the position of the mouse cursor of the server is automatically moved by an application, for example, the client side cannot grasp the position of the moved mouse cursor of the server, and therefore cannot cope with the moved position. Similarly, even if the server mouse cursor shape automatically changes, the client side cannot respond.

  Even in the disclosed technique in the server drawing method, when the client moves the cursor, the shape of the cursor is drawn based on the object area corresponding to the movement position of the cursor accordingly. Therefore, it is the same that the client side cannot respond when the shape of the mouse cursor of the server automatically changes.

  An object of the disclosed technique is to allow a client mouse to respond to a change in the mouse cursor of the server while maintaining the response performance of the local echo mouse cursor in the screen transfer method.

  In one aspect, the pointer position correction method is a pointer position correction method executed by a server, and includes an event accompanying movement of a pointer and a pointer after movement input by a client connected to the server via a network. When the event information including the position is received from the client, the received event information is stored in the event history, and processing is performed based on the event information, there is a change in the position of the pointer before and after the processing. It is determined whether or not the pointer position matches the pointer position of any event information stored in the event history, and as a result of the determination process, the pointer position that has changed is the event When it is determined that it does not match the pointer position of any event information stored in the history Includes each process of notifying the position of the pointer that was a said change in said client.

  According to one aspect of the pointer position correcting method disclosed in the present application, a change in the mouse cursor of the server can be made to correspond to the client while maintaining the response performance of the local echo mouse cursor.

FIG. 1 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the first embodiment. FIG. 2 is a diagram illustrating an example of a data structure of the input event history holding unit. FIG. 3 is a diagram illustrating a specific example of cursor position correction according to the first embodiment. FIG. 4 is a flowchart illustrating the procedure of the input event process in the client device according to the first embodiment. FIG. 5 is a flowchart illustrating the procedure of the screen drawing process in the client device according to the first embodiment. FIG. 6 is a flowchart illustrating the procedure of the input event process in the server apparatus according to the first embodiment. FIG. 7 is a flowchart illustrating the procedure of the cursor position correction process in the server apparatus according to the first embodiment. FIG. 8 is a flowchart illustrating the procedure of the screen information transfer process in the server apparatus according to the first embodiment. FIG. 9 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the second embodiment. FIG. 10 is a diagram illustrating a specific example of cursor position correction according to the second embodiment. FIG. 11 is a flowchart illustrating the procedure of the cursor position correction process in the server apparatus according to the second embodiment. FIG. 12 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the third embodiment. FIG. 13 is a diagram illustrating a specific example of cursor position correction according to the third embodiment. FIG. 14 is a flowchart illustrating the procedure of the screen drawing process in the client device according to the third embodiment. FIG. 15 is a flowchart illustrating the procedure of the cursor position correction process in the server device according to the third embodiment. FIG. 16 is a diagram for explaining a problem in the local echo method. FIG. 17 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the fourth embodiment. FIG. 18 is a diagram illustrating a specific example of cursor position correction according to the fourth embodiment. FIG. 19 is a flowchart illustrating a procedure of input event processing in the client device according to the fourth embodiment. FIG. 20 is a flowchart illustrating the procedure of the cursor movement direction limiting process in the client device according to the fourth embodiment. FIG. 21 is a flowchart illustrating the procedure of the cursor position correction process in the server apparatus according to the fourth embodiment. FIG. 22 is a diagram illustrating an example of a computer that executes a cursor position correction program. FIG. 23 is a diagram for explaining a server drawing method that is a drawing method of a mouse cursor. FIG. 24 is a diagram for explaining a local echo method which is a drawing method of a mouse cursor.

  Hereinafter, embodiments of a pointer position correcting method, a pointer position correcting program, and a server device disclosed in the present application will be described in detail with reference to the drawings. In the embodiment, the pointer is described as a cursor that moves in accordance with a mouse operation. Further, the present invention is not limited to the embodiments.

[Configuration of each device included in the thin client system]
FIG. 1 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the first embodiment. A thin client system 9 shown in FIG. 1 allows the server device 2 to remotely control the desktop screen displayed by the client device 1. In other words, the thin client system 9 behaves as if the client device 1 has executed the processing while displaying the processing result or the like executed by the server device 2 on the client device 1 in practice.

  As shown in FIG. 1, the thin client system 9 includes a client device 1 and a server device 2. In the example of FIG. 1, the case where one client device 1 is connected to one server device 2 is illustrated, but any number of client devices 1 can be connected.

  The client device 1 and the server device 2 are connected via a network 3 so that they can communicate with each other. For such a network, any type of communication network such as the Internet, a LAN (Local Area Network), a VPN (Virtual Private Network), or the like can be adopted regardless of wired or wireless. As an example, a screen transfer method in VNC is adopted as a communication protocol between server device 2 and client device 1. That is, the contents of the desktop screen of the server device 2 are transferred to the client as an image such as a bitmap or JPEG, and the transferred image is displayed on the desktop screen of the client device 1.

  The server device 2 is a computer that provides a service for remotely controlling a screen displayed on the client device 1. The client device 1 is a computer that receives a remote screen control service provided by the server device 2. As an example of the client device 1, a mobile terminal such as a mobile phone, a PHS (Personal Handyphone System), and a PDA (Personal Digital Assistant) can be applied in addition to a fixed terminal such as a personal computer.

[Configuration of client device]
The client device 1 includes an OS (Operating System) 10, an input event processing unit 11, and a screen drawing unit 12. The OS 10 provides input / output functions including input from the mouse and keyboard and output to the screen, and manages the entire client device 1. An example of the OS 10 is Windows (registered trademark), but another OS such as UNIX (registered trademark) may be used. The input event processing unit 11 processes an input event generated by operating a mouse or a keyboard. Further, the input event processing unit 11 includes an input event acquisition unit 111, an input event transmission unit 112, and a cursor drawing unit 113. Further, the screen drawing unit 12 corrects the cursor position according to the information (cursor position correction information) received from the server device 2 and corrects the cursor position, or draws the screen according to the screen information received from the server device 2. To do. Furthermore, the screen drawing unit 12 includes a cursor position correction information receiving unit 121, a cursor position correcting unit 122, a screen information receiving unit 123, an image development processing unit 124, and a screen information drawing unit 125.

  The input event acquisition unit 111 acquires an input event from an input / output device such as a keyboard or a mouse connected to the client device 1. The input event refers to an event for moving the cursor by a mouse movement operation, for example. As an example of the input event, there is “MOUSE_MOVE mouse X coordinate, mouse Y coordinate, wheel movement amount”. “MOUSE_MOVE” is a mouse operation content, and here indicates a mouse movement operation. The X coordinate of the mouse and the Y coordinate of the mouse respectively indicate the X coordinate position and the Y coordinate position of the movement destination of the mouse. The amount of movement of the wheel indicates the amount of movement when the wheel is used for movement. As a specific example, there is “MOUSE_MOVE 800, 600, 0” in which the X coordinate of the mouse is 800, the Y coordinate of the mouse is 600, and the movement amount of the wheel is 0.

  The input event acquisition unit 111 causes the input event transmission unit 112 described later to transmit the acquired input event to the server device 2 and causes the cursor drawing unit 113 described later to draw a mouse cursor at a position after the event processing. The input event transmission unit 112 transmits the input event acquired by the input event acquisition unit 111 to the server device 2.

  The cursor drawing unit 113 redraws the mouse cursor on the desktop screen of the client device 1. For example, the cursor drawing unit 113 extracts the movement destination position of the mouse cursor included in the input event acquired by the input event acquisition unit 111. Then, the cursor drawing unit 113 draws the mouse cursor at the position of the extracted mouse cursor on the desktop screen of the own device. That is, the input event processing unit 11 transmits the generated input event to the server device 2 as in the local echo method, and redraws the mouse cursor corresponding to the generated input event on its own device.

  Further, the cursor drawing unit 113 acquires the correction position of the mouse cursor from a cursor position correction unit 122 described later, and draws the mouse cursor at the correction position of the acquired mouse cursor on the desktop screen of the own device.

  The cursor position correction information receiving unit 121 receives cursor position correction information from the server device 2. Here, the cursor position correction information is cursor position information corrected by the server device 2. That is, in the server apparatus 2, as a result of processing the input event transmitted from the client apparatus 1, the position of the processed mouse cursor may be automatically changed by the OS. For example, depending on the operation of the OS, it may be set to automatically move to a specific button. In such a case, the cursor position correction information receiving unit 121 receives the cursor position correction information from the server apparatus 2 and corrects the cursor position using the received cursor position correction information to correspond to the cursor position of the server apparatus 2.

  The cursor position correction unit 122 extracts the correction position of the mouse cursor from the cursor position correction information received by the cursor position correction information reception unit 121. In addition, the cursor position correction unit 122 causes the cursor drawing unit 113 to redraw at the correction position of the extracted mouse cursor.

  The screen information receiving unit 123 receives the compressed screen display data from the server device 2. The image expansion processing unit 124 expands the compressed screen display data received by the screen information receiving unit 123. The screen information drawing unit 125 redraws the screen contents using the screen display data developed by the image development processing unit 124. In the embodiment, the image processing other than the mouse cursor follows the screen transfer method, and is simply described.

[Configuration of server device]
The server device 2 includes an OS 20, an input event history holding unit 21, an input event processing unit 22, a cursor position correction unit 23, and a screen information transfer unit 24. The OS 20 provides an event processing function such as an input event and manages the entire server device 2. An example of the OS 20 is Windows (registered trademark), but another OS such as UNIX (registered trademark) may be used. The input event history holding unit 21 holds event information of an input event received from the client device 1 in the queue as an event history.

  Here, the data structure of the input event history holding unit 21 will be described with reference to FIG. FIG. 2 is a diagram illustrating an example of a data structure of the input event history holding unit. As illustrated in FIG. 2, the input event history holding unit 21 associates an X coordinate 21 a and a Y coordinate 21 b for each input event, and holds the input event history. The X coordinate 21a is the X coordinate position of the movement destination included in the input event. The Y coordinate 21b is the position of the Y coordinate of the movement destination included in the input event. The history of input events is held in the order in which the input events are transmitted from the client device 1 to the server device 2. As an example, as the history of the oldest input event in the first row, the X coordinate is “797” and the Y coordinate is “603”. As the newest input event history in the fourth row, the X coordinate is “800” and the Y coordinate is “600”.

  Returning to FIG. 1, the input event processing unit 22 receives an input event from the client device 1 and processes the received input event. Further, the input event processing unit 22 includes an input event receiving unit 221, an input event storage unit 222, and an input event execution unit 223. The cursor position correction unit 23 corrects the cursor position of the client device 1 using the input event history holding unit 21. Furthermore, the cursor position correction unit 23 includes a cursor position change check unit 231, a cursor position history check unit 232, and a cursor position correction information transmission unit 233. The screen information transfer unit 24 transfers the screen information to the client device 1. Furthermore, the screen information transfer unit 24 includes a screen information acquisition unit 241, a screen update determination unit 242, an image compression processing unit 243, and a screen information transmission unit 244.

  The input event receiving unit 221 receives an input event transmitted from the client device 1. The input event storage unit 222 stores the input event received by the input event reception unit 221 in the input event history storage unit 21 as an input event history.

  The input event execution unit 223 executes the input event received by the input event reception unit 221. For example, the input event execution unit 223 passes the input event received by the input event reception unit 221 to the OS 20 for processing.

  The cursor position change check unit 231 determines whether or not the cursor position has changed before and after execution as a result of the input event being executed by the input event execution unit 223. For example, as a result of causing the OS 20 to process the input event, the cursor position change check unit 231 acquires the position of the mouse cursor corresponding to the processing from the OS 20. Then, the cursor position change checking unit 231 determines whether or not the acquired position of the mouse cursor matches the position of the mouse cursor before the input event is processed. The cursor position change check unit 231 checks, for example, a screen update determination unit 242 (described later) after each frame of screen display data is updated.

  If the cursor position change check unit 231 determines that the cursor position change has occurred before and after execution by the cursor position change check unit 231, whether the cursor position change has been held in the input event history holding unit 21. Check if. For example, the cursor position history check unit 232 determines whether or not the position of the mouse cursor that has changed matches any of the coordinate positions held as the input event history in the input event history holding unit 21. .

  When the cursor position history check unit 232 determines that the changed mouse cursor position is held in the input event history holding unit 21, the history of the input event determined to be held and the history before the history Is deleted. That is, the cursor position history check unit 232 deletes the history before the history of the processed input event because the position of the mouse cursor as a result of processing by the OS 20 has not been automatically changed by the OS 20. On the other hand, when the cursor position history check unit 232 determines that the changed mouse cursor position is not held in the input event history holding unit 21, the cursor position history check unit 232 indicates the changed mouse cursor position as the cursor position correction information transmission unit. 233 is notified. That is, the cursor position history check unit 232 determines that the position of the mouse cursor, which is the result processed by the OS 20, has been automatically changed by the OS 20, and sends the changed mouse cursor position to the cursor position correction information transmission unit 233. Notice.

  The cursor position correction information transmission unit 233 transmits the cursor position correction information including the cursor position notified by the cursor position history check unit 232 to the client device 1. Thereby, the position of the mouse cursor automatically changed by the OS 20 can be corrected by the client device 1.

  The screen information acquisition unit 241 acquires screen display data via the OS 20. The screen update determination unit 242 uses the screen information acquisition unit 241 to compare the screen display data acquired last time with the screen display data acquired this time, and determines whether or not the screen display data has been updated. When the screen update determination unit 242 determines that the screen display data has been updated, the image compression processing unit 243 compresses the screen display data in the updated area. The screen information transmission unit 244 transmits the compressed screen display data compressed by the image compression processing unit 243 to the client device 1.

[Specific example of cursor position correction]
Next, a specific example of cursor position correction will be described with reference to FIG. FIG. 3 is a diagram illustrating a specific example of cursor position correction according to the first embodiment.

  As shown in FIG. 3, in the client device 1, the input event acquisition unit 111 acquires an input event from the mouse connected to the client device 1 (step S1). Here, it is assumed that the input event is an event in which the movement destination of the mouse becomes (x2, y2) by the movement operation of the mouse.

  The input event acquisition unit 111 passes the acquired input event to the input event transmission unit 112 and the cursor drawing unit 113. Then, the input event transmission unit 112 transmits the delivered input event to the server device 2, and the cursor drawing unit 113 draws the delivered input event on the desktop screen via the OS 10 (step S2). Here, the cursor drawing unit 113 draws a cursor on P2 of the desktop screen.

  In the server device 2, the input event receiving unit 221 receives the input event transmitted from the client device 1. Then, the input event storage unit 222 holds the input event received by the input event reception unit 221 as an event history. Here, the input event storage unit 222 holds the coordinate P2 of the movement destination included in the input event as an event history. In addition, the input event execution unit 223 causes the OS 20 to process the input event received by the input event reception unit 221 (step S3).

  Then, the cursor position change check unit 231 acquires the coordinates of the mouse cursor that is the result of processing performed by the OS 20 (step S4). Then, the cursor position change check unit 231 determines that the acquired mouse cursor coordinates P2 do not match the coordinates of the mouse cursor before processing, that is, the mouse cursor has moved. Then, the cursor position history check unit 232 determines whether or not the coordinate P2 of the processed mouse cursor is held as an input event history (step S5). Here, since the coordinate P2 of the mouse cursor after processing is held as the input event history, the history before the coordinate P2 is deleted (step S6). As described above, for example, in the case of an input event in which the movement destination of the mouse is the coordinate P2, the coordinate P2 of the mouse cursor after the processing is not automatically changed by the OS 20, so the coordinate correction is performed on the client device 1. However, the process is terminated. As a result, the coordinates of the mouse cursors of the client device 1 and the server device 2 are drawn on P2.

  Next, the case of an input event in which the mouse destination is the coordinate P3 (x3, y3) will be described. In the client device 1, the input event acquisition unit 111 passes the input event acquired from the mouse to the input event transmission unit 112 and the cursor drawing unit 113. Then, the input event transmission unit 112 transmits the delivered input event to the server device 2, and the cursor drawing unit 113 draws the delivered input event on the desktop screen via the OS 10 (step S2). Here, the cursor drawing unit 113 draws the cursor on P3 of the desktop screen.

  In the server device 2, the input event receiving unit 221 receives the input event transmitted from the client device 1. Then, the input event storage unit 222 holds the input event received by the input event reception unit 221 as an event history. Here, the input event storage unit 222 holds the coordinate P3 of the movement destination included in the input event as an event history. In addition, the input event execution unit 223 causes the OS 20 to process the input event received by the input event reception unit 221 (step S3).

  Then, the cursor position change check unit 231 acquires the coordinates of the mouse cursor after being processed by the OS 20 (step S4). Here, it is assumed that the position of the mouse cursor is automatically changed from P3 to P4 (x4, y4) by the OS 20. Then, the cursor position change check unit 231 determines that the acquired mouse cursor coordinate P4 does not match the mouse cursor coordinate P2 before processing. Then, the cursor position history check unit 232 determines whether or not the coordinate P4 of the processed mouse cursor is held as an input event history (step S5). Here, since the coordinate P4 of the mouse cursor after the processing is automatically changed from the movement destination coordinate P3 included in the input event by the OS 20, the coordinate P4 is not held as the input event history. Thus, the cursor position history check unit 232 notifies the cursor position correction information transmission unit 233 of the changed mouse cursor coordinates P4 (step S7).

  In the client device 1, the cursor position correction information receiving unit 121 receives the changed coordinates P4 of the mouse cursor. The cursor position correcting unit 122 causes the cursor drawing unit 113 to redraw the mouse cursor at the changed coordinate P4 of the mouse cursor. As described above, even if the coordinates of the mouse cursor after the processing are automatically changed by the OS 20 as a result of processing the input event transmitted from the client device 1 by the server device 2, the changed coordinates correspond to the client device 1. Can be made.

[Input event processing procedure in client device]
Next, the procedure of input event processing in the client device 1 will be described with reference to FIG. FIG. 4 is a flowchart illustrating the procedure of the input event process in the client device according to the first embodiment.

  First, the input event acquisition unit 111 determines whether there is an unprocessed input event (step S11). When it is determined that there is no unprocessed input event (step S11; No), the input event acquisition unit 111 repeats the determination process until it is determined that there is an unprocessed input event.

  On the other hand, when it is determined that there is an unprocessed input event (step S11; Yes), the input event acquisition unit 111 acquires the input event (step S12). Then, the cursor drawing unit 113 redraws the mouse cursor on the desktop screen of its own device based on the input event acquired by the input event acquisition unit 111 (step S13). For example, the cursor drawing unit 113 extracts the position of the destination mouse cursor included in the input event, and redraws the mouse cursor at the extracted mouse cursor position.

  Then, the input event transmission unit 112 transmits the input event acquired by the input event acquisition unit 111 to the server device 2 (step S14). Then, the input event processing unit 11 proceeds to step S11 in order to wait for the next event to occur.

[Procedure for screen drawing processing on client device]
Next, the procedure of the screen drawing process in the client device 1 will be described with reference to FIG. FIG. 5 is a flowchart illustrating the procedure of the screen drawing process in the client device according to the first embodiment.

  First, the screen drawing unit 12 determines whether or not data related to a screen transfer method has been received from the server device 2 (step S21). If it is determined that data related to the screen transfer method has not been received (step S21; No), the screen drawing unit 12 repeats the determination process until data related to the screen transfer method is received.

  If it is determined that data related to the screen transfer method has been received (step S21; Yes), it is determined whether the cursor position correction information receiving unit 121 has received the cursor position correction information (step S22). When it is determined that the cursor position correction information has been received (step S22; Yes), the cursor position correction information receiving unit 121 receives the cursor position correction information (step S23).

  Subsequently, the cursor position correction unit 122 extracts a correction position from the received cursor position correction information, and corrects the position of the mouse cursor to the extracted correction position (step S24). The cursor drawing unit 113 redraws the mouse cursor at the corrected position (step S25). Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

  If it is determined in step S22 that the cursor position correction information has not been received (step S22; No), the screen information receiving unit 123 determines whether screen information has been received (step S26). When it is determined that the screen information has been received (step S26; Yes), the screen information receiving unit 123 receives the compressed screen display data (step S27).

  Subsequently, the image expansion processing unit 124 expands the compressed screen display data (step S28). Then, the screen information drawing unit 125 redraws the desktop screen using the screen display data obtained by the expansion (step S29). Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

  If it is determined in step S26 that screen information has not been received (step S26; No), the screen information receiving unit 123 has received data unrelated to the screen transfer method, so nothing is done here (step S30). . Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

[Procedure for input event processing in server device]
Next, the procedure of input event processing in the server device 2 will be described with reference to FIG. FIG. 6 is a flowchart illustrating the procedure of the input event process in the server apparatus according to the first embodiment.

  First, the input event receiving unit 221 of the server device 2 determines whether or not an input event has been received from the client device 1 (step S31). When it is determined that an input event has not been received (step S31; No), the input event reception unit 221 repeats the determination process until an input event is received.

  On the other hand, when it determines with having received the input event (step S31; Yes), the input event receiving part 221 receives an input event (step S32). The input event storage unit 222 stores the received input event as an input event history in the input event history storage unit 21 (step S33).

  Subsequently, the input event execution unit 223 delivers the input event to the OS 20 and causes the OS 20 to process it (step S34). Then, the input event processing unit 22 proceeds to step S31 in order to wait for reception of the next event.

[Procedure for cursor position correction processing in server device]
Next, the procedure of the cursor position correction process in the server device 2 will be described with reference to FIG. FIG. 7 is a flowchart illustrating the procedure of the cursor position correction process in the server apparatus according to the first embodiment.

  The cursor position change checking unit 231 determines whether or not a predetermined time has elapsed (step S41). When it is determined that the predetermined time has not elapsed (step S41; No), the cursor position change check unit 231 repeats the determination process until the predetermined time has elapsed.

  On the other hand, when it is determined that a predetermined time has elapsed (step S41; Yes), the cursor position change check unit 231 checks whether or not the mouse cursor has moved (step S42). For example, as a result of causing the OS 20 to process the input event, the cursor position change check unit 231 acquires the position of the mouse cursor corresponding to the processing from the OS 20. Then, the cursor position change checking unit 231 determines whether or not the acquired position of the mouse cursor matches the position of the mouse cursor before the input event is processed. Here, the predetermined time indicates, for example, the update time of the screen display data of one frame, and is 33 ms as an example.

  If it is determined that the mouse cursor has not moved (step S42; No), the cursor position correction unit 23 ends the cursor position correction process and proceeds to a screen information transfer process. On the other hand, when it is determined that the mouse cursor has moved (step S42; Yes), the cursor position history check unit 232 determines whether or not there is an input event corresponding to the position of the mouse cursor after the movement (step S43). ). For example, the cursor position history check unit 232 determines whether or not the position of the mouse cursor that has changed matches any of the coordinate positions held as the input event history in the input event history holding unit 21. .

  If it is determined that the corresponding input event exists (step S43; Yes), the cursor position history check unit 232 deletes the history before the history of the corresponding input event (step S44). Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

  On the other hand, when it is determined that there is no corresponding input event (step S43; No), the cursor position history check unit 232 determines that the cursor position has been automatically changed by the OS 20. Then, the cursor position history check unit 232 causes the cursor position correction information transmission unit 233 to transmit the cursor position correction information to the client device 1 (step S45). For example, the cursor position correction information transmission unit 233 transmits the cursor position correction information including the changed cursor position to the client device 1. Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

[Procedure for screen information transfer processing in server device]
Next, the procedure of the screen information transfer process in the server device 2 will be described with reference to FIG. FIG. 8 is a flowchart illustrating the procedure of the screen information transfer process in the server apparatus according to the first embodiment.

  The screen information acquisition unit 241 acquires screen display data via the OS 20 (step S51). Then, the screen update determination unit 242 compares the acquired screen display data with the previously acquired screen display data to determine whether or not there has been a screen update (step S52). If it is determined that the screen has not been updated (step S52; No), the screen information transfer unit 24 transitions to step S41 to shift to the cursor position correction process.

  On the other hand, when it is determined that the screen has been updated (step S52; Yes), the image compression processing unit 243 compresses the screen display data in the updated area (step S53). Then, the screen information transmitting unit 244 transmits the compressed screen display data to the client device 1 (Step S54). Then, the screen information transfer unit 24 transitions to step S41 to shift to the cursor position correction process.

[Effect of Example 1]
According to the first embodiment, the server device 2 of the thin client system 9 holds the event information including the position of the cursor after the movement for the input event accompanied by the movement of the mouse cursor received from the client device 1 as the input event history. Stored in the unit 21. Then, as a result of processing based on the input event, when the cursor position has changed before and after processing, the server device 2 is one of the cursor positions that have changed are held in the input event history holding unit 21 It is determined whether or not it coincides with the position of the cursor. Then, the server device 2 determines that the changed cursor position does not coincide with any cursor position held in the input event history holding unit 21 as a result of the determination. The client device 1 is notified of the position. According to such a configuration, the server apparatus 2 can move even if the position of the cursor that has changed before and after the process is automatically moved by the process based on the input event received from the client apparatus 1. The position of the subsequent cursor can be made to correspond to the client device 1.

  Further, according to the first embodiment, when the server apparatus 2 matches the position of any cursor held in the input event history holding unit 21 as a result of the determination, The event information before the event related to the position of the matched cursor is deleted. According to such a configuration, the server device 2 can reduce the number of comparisons with the position of the cursor held in the input event history holding unit 21 in the next process related to the input event, thereby increasing the processing efficiency. it can.

  By the way, in the server device 2 according to the first embodiment, when it is determined that the position of the mouse cursor that has changed before and after the processing of the input event is held in the input event history holding unit 21, it is determined that it is held. Described the case of deleting the history before the input event history. However, if the server apparatus 2 determines that the position of the mouse cursor that has changed is held in the input event history holding unit 21, the server apparatus 2 has a long queue before the history is deleted. Alternatively, the processing interval of the screen transfer method may be adjusted.

  That is, in the server apparatus 2, the processing load in the screen transfer method may increase. In such a case, the server device 2 may have a longer processing time for the input event transmitted from the client device 1, and the input event queue held in the input event history holding unit 21 may be longer. Therefore, the server device 2 may reduce the processing load by adjusting the processing interval of the screen transfer method when the queue length is larger than the threshold value.

  Therefore, in the second embodiment, a description will be given of the server device 2 that adjusts the processing interval of the screen transfer method when the queue length of the input event held in the input event history holding unit 21 is larger than the threshold value.

[Configuration of each device included in the thin client system]
FIG. 9 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the second embodiment. In addition, about the same structure as the thin client system 9 shown in FIG. 1, the same code | symbol is shown, The description of the overlapping structure and operation | movement is abbreviate | omitted. The difference between the first embodiment and the second embodiment is that an input event history retention number check unit 301 is added to the cursor position correction unit 23 of the server device 2A.

  The cursor position history check unit 232 checks whether or not the cursor position where the cursor position has changed before and after execution of the input event is held in the input event history holding unit 21.

  When the position of the mouse cursor that has changed is held in the input event history holding unit 21, the input event history holding number check unit 301 sets the queue length of the input event held in the input event history holding unit 21 as a threshold value. It is determined whether it is above. For example, the input event history holding number check unit 301 includes an input event before an input event related to a coordinate position that matches the position of the mouse cursor that has changed in the input event history held in the input event history holding unit 21. Count the number of. Also, the input event history retention number check unit 301 determines whether or not the counted number of input events is greater than a threshold value. If the input event history retention count check unit 301 determines that the number of input events counted is greater than the threshold, the input event history retention count check unit 301 determines that the processing load is high, and sets the processing interval of the screen transfer method to be greater than the current processing interval. Enlarge. On the other hand, if the input event history retention number check unit 301 determines that the number of input events counted is equal to or less than the threshold, the input event history retention number check unit 301 determines that the processing load is low, and sets the screen transfer method processing interval to be greater than the current processing interval. Decrease or keep the current processing interval. Then, the input event history retention number check unit 301 deletes the history before the input event history related to the coordinate position that matched.

  The threshold value to be compared with the number of input events is, for example, 3. However, it may be changed according to the processing performance of the CPU, and may be a value determined to increase the processing load. The processing interval of the screen transfer method refers to a screen update interval (update frequency). That is, the cursor position change check unit 231 coincides with a predetermined time which is a time interval for checking whether or not the mouse cursor has moved. That is, if the processing interval of the screen transfer method increases, the predetermined time increases, and if the processing interval of the screen transfer method decreases, the predetermined time also decreases.

[Specific example of cursor position correction]
Next, a specific example of cursor position correction will be described with reference to FIG. FIG. 10 is a diagram illustrating a specific example of cursor position correction according to the second embodiment.

  As illustrated in FIG. 10, in the client device 1A, the input event acquisition unit 111 acquires an input event from a mouse connected to the client device 1 (step S1). Here, the input event is assumed to be three events in which the movement destination of the mouse moves to (x1, y1), (x2, y2), and (x3, y3) in time series by the movement operation of the mouse.

  The input event acquisition unit 111 acquires each input event in time series, and delivers the acquired input event to the input event transmission unit 112 and the cursor drawing unit 113 each time it is acquired. Then, the input event transmitting unit 112 transmits each delivered input event to the server device 2A, and the cursor drawing unit 113 renders each delivered input event on the desktop screen via the OS 10 (step S2). . Here, the cursor drawing unit 113 draws the cursor on P1 of the desktop screen, and then draws the cursor on P2 and P3.

  In the server device 2A, the input event receiving unit 221 receives each input event transmitted from the client device 1A in time series. Then, the input event storage unit 222 holds each input event received by the input event reception unit 221 as an event history. Here, the input event storage unit 222 holds the coordinates P1, P2, and P3 of the movement destination included in each input event as an event history. In addition, the input event execution unit 223 causes the OS 20 to process each input event received by the input event reception unit 221 (step S3).

  Then, the cursor position change check unit 231 acquires the coordinates of the mouse cursor that is the result of processing performed by the OS 20 (step S4). Then, the cursor position change check unit 231 determines that the acquired mouse cursor coordinates P1 do not match the coordinates of the mouse cursor before processing, that is, the mouse cursor has moved. Then, the cursor position history check unit 232 determines whether or not the coordinate P1 of the mouse cursor after processing is held as the input event history. Here, it is determined that the coordinate P1 of the processed mouse cursor is held as the input event history. Therefore, the input event history retention number check unit 301 checks the queue length before the corresponding input event in the input event history, and determines whether or not the queue length is larger than the threshold (step S5A). Here, since there are four input events (corresponding to P1, Px, Py, and Pz) before the input event corresponding to P1, the queue length is 4. When the threshold is 3, it is determined that the queue length (4) is larger than the threshold (3).

  Since the input event history retention number check unit 301 determines that the queue length is greater than the threshold, it determines that the processing load is high and increases the processing interval of the screen transfer method. Then, the input event history retention number check unit 301 deletes the history before the input event history related to the coordinate P1 of the mouse cursor after processing (step S6). Here, the history of input events related to P1, Px, Py, and Pz is deleted. Subsequently, the process of the screen information transfer unit 24 is executed. As described above, the server device 2A determines that the processing load is high when the queue length of the input event history is long, and reduces the processing load by increasing the processing interval of the screen transfer method. Can be improved.

[Procedure for cursor position correction processing in server device]
Next, the procedure of the cursor position correction process in the server device 2A will be described with reference to FIG. FIG. 11 is a flowchart illustrating the procedure of the cursor position correction process in the server apparatus according to the second embodiment. In addition, the same code | symbol is shown about the process same as the cursor position correction process in the server apparatus based on Example 1 shown in FIG.

  The cursor position change checking unit 231 determines whether or not a predetermined time has elapsed (step S41). When it is determined that the predetermined time has not elapsed (step S41; No), the cursor position change check unit 231 repeats the determination process until the predetermined time has elapsed.

  On the other hand, when it is determined that a predetermined time has elapsed (step S41; Yes), the cursor position change check unit 231 checks whether or not the mouse cursor has moved (step S42). For example, as a result of causing the OS 20 to process the input event, the cursor position change check unit 231 acquires the position of the mouse cursor corresponding to the processing from the OS 20. Then, the cursor position change check unit 231 determines whether or not the acquired position of the mouse cursor matches the position of the mouse cursor before the input event is processed (step S42). Here, the predetermined time indicates, for example, the update time of the screen display data of one frame.

  If it is determined that the mouse cursor has not moved (step S42; No), the cursor position correction unit 23 ends the cursor position correction process and proceeds to a screen information transfer process. On the other hand, when it is determined that the mouse cursor has moved (step S42; Yes), the cursor position history check unit 232 determines whether or not there is an input event corresponding to the position of the mouse cursor after the movement (step S43). ). For example, the cursor position history check unit 232 determines whether or not the position of the mouse cursor that has changed matches any of the coordinate positions held as the input event history in the input event history holding unit 21. .

  If it is determined that there is a corresponding input event (step S43; Yes), the input event history retention count checking unit 301 counts the number of input events (queue length) before the corresponding input event (step S401). For example, the input event history holding number check unit 301 includes an input event before an input event related to a coordinate position that matches the position of the mouse cursor that has changed in the input event history held in the input event history holding unit 21. Count the number of.

  Then, the input event history retention count checking unit 301 determines whether or not the queue length is larger than the threshold (step S402). When it is determined that the queue length is greater than the threshold (step S402; Yes), the input event history retention number check unit 301 determines that the processing load is high, and increases the processing interval of the screen transfer method (step S403).

  On the other hand, when it is determined that the queue length is equal to or smaller than the threshold (step S402; No), the input event history retention number check unit 301 determines that the processing load is low and reduces the processing interval of the screen transfer method (step S404). ). Then, the input event history retention number check unit 301 deletes the history before the history of the corresponding input event (step S44). Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

  Returning to step S43, if it is determined that the corresponding input event does not exist (step S43; No), the cursor position history check unit 232 determines that the cursor position has been automatically changed by the OS 20. Then, the cursor position history check unit 232 causes the cursor position correction information transmission unit 233 to transmit the cursor position correction information to the client device 1A (step S45). For example, the cursor position correction information transmission unit 233 transmits cursor position correction information including the changed cursor position to the client device 1A. Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

[Effect of Example 2]
According to the second embodiment, the server apparatus 2A of the thin client system 9 holds the event information including the position of the cursor after the movement for the input event accompanied by the movement of the mouse cursor received from the client apparatus 1A. Stored in the unit 21. Then, as a result of processing based on the input event, when the cursor position has changed before and after processing, the server apparatus 2A is one of the cursor positions that have changed are held in the input event history holding unit 21. It is determined whether or not it coincides with the position of the cursor. Then, the server apparatus 2A determines that the event related to the matched cursor position when the position of the cursor that has changed as a result of the determination matches the position of any of the cursors held in the input event history holding unit 21. It is determined whether the number of previous events is greater than a threshold value. If the server device 2A determines that the number of events before the event related to the matched cursor position is greater than the threshold, the server device 2A sets the processing interval of the screen transfer method to be larger than the current processing interval. According to such a configuration, when the number of corresponding events held in the input event history holding unit 21 is larger than the threshold, the server apparatus 2A has a longer interval of input event processing accompanied by movement of the cursor position. Therefore, it is assumed that the processing load of the own device is high. Therefore, the server device 2 can reduce the processing load by increasing the processing interval of the screen transfer method. As a result, the server apparatus 2A can improve the operability of the thin client system 9.

  By the way, in the server device 2 according to the first embodiment, the case where the mouse cursor is automatically moved by the processing of the input event and the position of the automatically moved mouse cursor is transmitted to the client device 1 has been described. However, the server device 2 is not limited to this, and when the mouse cursor moves automatically, the server device 2 may transmit the position and shape of the automatically moved mouse cursor to the client device 1. This is because when the position of the mouse cursor is automatically moved, the shape of the mouse cursor may change depending on the position after the movement.

  Thus, in the third embodiment, a description will be given of the server device 2 that transmits the position and shape of the automatically moved mouse cursor to the client device 1 when the mouse cursor automatically moves.

[Configuration of each device included in the thin client system]
FIG. 12 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the third embodiment. In addition, about the same structure as the thin client system 9 shown in FIG. 1, the same code | symbol is shown, The description of the overlapping structure and operation | movement is abbreviate | omitted. The difference between the first embodiment and the third embodiment is that a cursor shape check unit 401 and a cursor shape correction information transmission unit 402 are added to the cursor position correction unit 23 of the server device 2B. The difference between the first embodiment and the third embodiment is that a cursor shape correction information receiving unit 403 and a cursor shape correcting unit 404 are added to the screen drawing unit 12 of the client apparatus 1B.

  The cursor position history check unit 232 checks whether or not the cursor position where the cursor position has changed before and after execution of the input event is held in the input event history holding unit 21.

  When the position of the mouse cursor that has changed is not held in the input event history holding unit 21, the cursor shape check unit 401 further checks whether or not the shape of the mouse cursor has changed. For example, the cursor shape check unit 401 uses the OS 20 to determine whether the shape of the mouse cursor has changed. Then, when the shape of the mouse cursor changes, the cursor shape check unit 401 notifies the cursor shape correction information transmission unit 402 of the changed shape of the mouse cursor. That is, the cursor shape check unit 401 notifies the cursor shape correction information transmission unit 402 of the changed shape when the shape also changes with the position of the mouse cursor automatically changed by the OS 20.

  The cursor shape correction information transmission unit 402 transmits the cursor shape correction information including the cursor shape notified by the cursor shape check unit 401 to the client device 1B. Accordingly, the server apparatus 2B can cause the client apparatus 1B to correct the shape of the mouse cursor that has changed with the position of the mouse cursor automatically changed by the OS 20.

  The cursor shape correction information receiving unit 403 receives cursor shape information from the server device 2B. Here, the cursor shape correction information is cursor shape information corrected by the server device 2B. That is, in the server apparatus 2B, as a result of processing the input event transmitted from the client apparatus 1B, the position and shape of the mouse cursor after processing may be automatically changed by the OS 20. In such a case, the cursor shape correction information receiving unit 403 receives the cursor shape correction information from the server device 2B, corrects the cursor shape using the received cursor shape correction information, and corresponds to the cursor shape of the server device 2B. Let

  The cursor shape correction unit 404 extracts the correction shape of the mouse cursor from the cursor shape correction information received by the cursor shape correction information reception unit 403. In addition, the cursor shape correcting unit 404 causes the cursor drawing unit 113 to redraw the mouse cursor having the extracted corrected shape.

[Specific example of cursor position correction]
Next, a specific example of cursor position correction will be described with reference to FIG. FIG. 13 is a diagram illustrating a specific example of cursor position correction according to the third embodiment. In FIG. 13, the server apparatus 2B receives from the client apparatus 1B an input event in which the mouse display position is moved by a mouse movement operation. Then, for each input event whose destination moves to P1 and P2 in the input event, the position of the cursor after processing is not automatically moved by the OS 20. Furthermore, for input events in which the destination moves from P2 to P3 among the input events, the cursor position after processing is automatically moved from P3 to P4 by the OS 20, and the cursor shape also changes from an arrow shape to a triangular shape. Let's take an example. Hereinafter, the case of an input event in which the destination moves from P2 to P3 will be described.

  As illustrated in FIG. 13, in the client device 1B, the input event acquisition unit 111 acquires an input event from a mouse connected to the client device 1B (step S1). Here, the input event acquisition unit 111 acquires an input event whose mouse destination is (x3, y3) by a mouse movement operation.

  The input event acquisition unit 111 passes the acquired input event to the input event transmission unit 112 and the cursor drawing unit 113. Then, the input event transmission unit 112 transmits the delivered input event to the server device 2B, and the cursor drawing unit 113 draws the delivered input event on the desktop screen via the OS 10 (step S2). Here, the cursor drawing unit 113 draws the cursor on P3 of the desktop screen.

  In the server device 2B, the input event receiving unit 221 receives the input event transmitted from the client device 1B. Then, the input event storage unit 222 holds the input event received by the input event reception unit 221 as an event history. Here, the input event storage unit 222 holds the coordinate P3 of the movement destination included in the input event as an event history. In addition, the input event execution unit 223 causes the OS 20 to process the input event received by the input event reception unit 221 (step S3).

  Then, the cursor position change check unit 231 acquires the coordinates of the mouse cursor after being processed by the OS 20 (step S4). Here, the OS 20 automatically changes the position of the mouse cursor from P3 to P4 (x4, y4). Then, the cursor position change check unit 231 determines that the changed coordinate P4 does not match the coordinate P2 of the mouse cursor before processing. Therefore, the cursor position history check unit 232 determines whether or not the coordinate P4 of the mouse cursor after processing is held as the input event history (step S5). Here, since the coordinate P4 of the mouse cursor after the processing is automatically changed from the coordinate P3 by the OS 20, it is not held as an input event history. Thus, the cursor position history check unit 232 notifies the cursor position correction information transmission unit 233 of the changed mouse cursor coordinates P4 (step S7).

  Furthermore, the cursor shape check unit 401 determines whether or not the shape of the mouse cursor has changed using the OS 20. Here, the shape of the mouse cursor after processing has changed from an arrow shape to a triangular shape. Therefore, the cursor shape check unit 401 notifies the cursor shape correction information transmission unit 402 of the changed triangular shape of the mouse cursor (step S8).

  In the client device 1B, the cursor position correction information receiving unit 121 receives the changed mouse cursor coordinates P4. The cursor position correcting unit 122 causes the cursor drawing unit 113 to redraw the mouse cursor at the changed coordinate P4 of the mouse cursor. Subsequently, the cursor shape correction information receiving unit 403 receives the changed mouse cursor shape. Then, the cursor shape correcting unit 404 causes the cursor drawing unit 113 to redraw the changed mouse cursor.

  As described above, even when the shape of the mouse cursor after processing is changed as a result of processing the input event transmitted from the client device 1B by the server device 2B, the changed shape of the mouse cursor corresponds to the client device 1B. Can be made.

[Procedure for screen drawing processing on client device]
Next, the procedure of the screen drawing process in the client device 1B will be described with reference to FIG. FIG. 14 is a flowchart illustrating the procedure of the screen drawing process in the client device according to the third embodiment. In addition, the same code | symbol is shown about the process same as the screen drawing process in the server apparatus based on Example 1 shown in FIG.

  First, the screen drawing unit 12 determines whether or not data related to a screen transfer method has been received from the server device 2 (step S21). If it is determined that data related to the screen transfer method has not been received (step S21; No), the screen drawing unit 12 repeats the determination process until data related to the screen transfer method is received.

  If it is determined that data related to the screen transfer method has been received (step S21; Yes), it is determined whether the cursor position correction information receiving unit 121 has received the cursor position correction information (step S22). When it is determined that the cursor position correction information has been received (step S22; Yes), the cursor position correction information receiving unit 121 receives the cursor position correction information (step S23).

  Subsequently, the cursor position correction unit 122 extracts a correction position from the received cursor position correction information, and corrects the position of the mouse cursor to the extracted correction position (step S24). The cursor drawing unit 113 redraws the mouse cursor at the corrected position (step S25). Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

  If it is determined in step S22 that the cursor position correction information has not been received (step S22; No), it is determined whether or not the cursor shape correction information receiving unit 403 has received the cursor shape correction information (step S61). When it is determined that the cursor shape correction information has been received (step S61; Yes), the cursor shape correction information receiving unit 403 receives the cursor shape correction information (step S62).

  Subsequently, the cursor shape correction unit 404 extracts a correction shape from the received cursor shape correction information, and corrects the shape of the mouse cursor to the extracted correction shape (step S63). Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

  If it is determined in step S61 that the cursor shape correction information has not been received (step S61; No), the screen information receiving unit 123 determines whether screen information has been received (step S26). When it is determined that the screen information has been received (step S26; Yes), the screen information receiving unit 123 receives the compressed screen display data (step S27).

  Subsequently, the image expansion processing unit 124 expands the compressed screen display data (step S28). Then, the screen information drawing unit 125 redraws the desktop screen using the screen display data obtained by the expansion (step S29). Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

  If it is determined in step S26 that screen information has not been received (step S26; No), the screen information receiving unit 123 has received data unrelated to the screen transfer method, so nothing is done here (step S30). . Then, the screen drawing unit 12 proceeds to step S21 in order to wait for data relating to the next screen transfer method.

[Procedure for cursor position correction processing in server device]
Next, the procedure of the cursor position correction process in the server device 2B will be described with reference to FIG. FIG. 15 is a flowchart illustrating the procedure of the cursor position correction process in the server device according to the third embodiment. In addition, the same code | symbol is shown about the process same as the cursor position correction process in the server apparatus based on Example 1 shown in FIG.

  The cursor position change checking unit 231 determines whether or not a predetermined time has elapsed (step S41). When it is determined that the predetermined time has not elapsed (step S41; No), the cursor position change check unit 231 repeats the determination process until the predetermined time has elapsed.

  On the other hand, when it is determined that a predetermined time has elapsed (step S41; Yes), the cursor position change check unit 231 checks whether or not the mouse cursor has moved (step S42). For example, as a result of causing the OS 20 to process the input event, the cursor position change check unit 231 acquires the position of the mouse cursor corresponding to the processing from the OS 20. Then, the cursor position change checking unit 231 determines whether or not the acquired position of the mouse cursor matches the position of the mouse cursor before the input event is processed. Here, the predetermined time indicates, for example, the update time of the screen display data of one frame.

  If it is determined that the mouse cursor has not moved (step S42; No), the cursor position correction unit 23 ends the cursor position correction process and proceeds to a screen information transfer process. On the other hand, when it is determined that the mouse cursor has moved (step S42; Yes), the cursor position history check unit 232 determines whether or not there is an input event corresponding to the position of the mouse cursor after the movement (step S43). ). For example, the cursor position history check unit 232 determines whether or not the position of the mouse cursor that has changed matches any of the coordinate positions held as the input event history in the input event history holding unit 21. .

  If it is determined that the corresponding input event exists (step S43; Yes), the cursor position history check unit 232 deletes the history before the history of the corresponding input event (step S44). Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

  On the other hand, when it is determined that there is no corresponding input event (step S43; No), the cursor position history check unit 232 determines that the cursor position has been automatically changed by the OS 20. Then, the cursor position history check unit 232 causes the cursor position correction information transmission unit 233 to transmit the cursor position correction information to the client device 1 (step S45). For example, the cursor position correction information transmission unit 233 transmits the cursor position correction information including the changed cursor position to the client device 1.

  Subsequently, the cursor shape check unit 401 determines whether or not the shape of the mouse cursor has changed. When it is determined that the shape of the mouse cursor has not changed (step S71; No), the cursor shape check unit 401 ends the cursor position correction process and proceeds to a screen information transfer process.

  On the other hand, if it is determined that the shape of the mouse cursor has changed (step S71; Yes), the cursor shape correction information transmission unit 402 causes the cursor shape correction information transmission unit 402 to transmit the cursor shape correction information to the client device 1B (step S71). S72). For example, the cursor shape correction information transmission unit 402 transmits the cursor shape correction information including the changed cursor shape to the client device 1B. Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

[Effect of Example 3]
According to the third embodiment, the server apparatus 2B of the thin client system 9 receives an input event accompanied by the movement of the mouse cursor from the client apparatus 1B. Then, the server device 2B stores event information including the position of the cursor after movement for the received input event in the input event history holding unit 21. Then, as a result of processing based on the input event, as a result of processing based on the input event, the server device 2B has one of the cursor positions that have changed before and after the processing held in the input event history holding unit 21. It is determined whether or not it coincides with the position of the cursor. Then, the server apparatus 2B determines that the cursor position that has changed is found when the cursor position that has changed as a result of the determination does not match any cursor position that is held in the input event history holding unit 21. The position is notified to the client device 1B. Further, as a result of processing based on the input event, the server device 2B notifies the client device 1B of the changed cursor shape when the cursor shape changes before and after the processing. According to such a configuration, the server device 2B changes the cursor shape after the change to the client device 1B even if the cursor shape has changed before and after the processing based on the input event received from the client device 1B. It can be made to correspond.

  By the way, in the server device 2 according to the first embodiment, the case has been described in which, when the mouse cursor is automatically moved by the processing of the input event, the position of the automatically moved mouse cursor is corrected to the client device 1. However, in the server device 2, the movement area of the mouse cursor may be limited. In such a case, in the client device 1, if the position of the mouse cursor to be drawn by the local echo method is within an area where movement is restricted by the server device 2, if the position corrected from the server device 2 is redrawn, Becomes unnatural.

  The problem in the local echo method will be described with reference to FIG. FIG. 16 is a diagram for explaining a problem in the local echo method. As shown in FIG. 16, the movement of the mouse cursor is restricted in the area G1 on the desktop screen of the server apparatus 2C. That is, on the desktop screen of the server device 2C, the movement of the mouse cursor is permitted in the area G2 other than the restricted area G1. Under such circumstances, it is assumed that an input event that moves in the direction of the region G1 ′ corresponding to the restricted region G1 repeatedly occurs on the client device 1C side. Then, each time the input event generated on the client device 1C side is received, the server device 2C side corrects the cursor position at the boundary between the restriction region G1 and the permission region G2, and the corrected cursor position is set to the client device 1C. Will be sent to. Then, on the client device 1C side, even if the cursor is once drawn by local echo when the input event occurs, the corrected cursor position transmitted from the server device 2C is redrawn. Becomes unnatural. In the example of FIG. 16, on the server device 2C side, the movement locus of the mouse cursor is only the X-axis direction (lateral direction) of the boundary between the restriction area G1 and the permission area G2. On the other hand, on the client device 1C side, the movement locus of the mouse cursor is jagged in the vertical direction, which is an unnatural locus.

  Thus, in the fourth embodiment, the server apparatus 2C that prevents the movement locus of the mouse cursor of the client apparatus 1C from becoming unnatural even when the movement area of the mouse cursor is limited by the server apparatus 2C will be described. .

[Configuration of each device included in the thin client system]
FIG. 17 is a functional block diagram illustrating the configuration of each device included in the thin client system according to the fourth embodiment. In addition, about the same structure as the thin client system 9 shown in FIG. 1, the same code | symbol is shown, The description of the overlapping structure and operation | movement is abbreviate | omitted. The difference between the first embodiment and the fourth embodiment is that a cursor movement direction determination unit 501 and a cursor movement direction notification unit 502 are added to the cursor position correction unit 23 of the server device 2C. Also, the difference between the first embodiment and the fourth embodiment is that a cursor movement direction restriction processing section 50 is added to the input event processing section 11 of the client apparatus 1C, and a cursor movement direction reception section 503 is added to the cursor movement direction restriction processing section 50. It is in the point that was added. Further, the difference between the first embodiment and the fourth embodiment is that a cursor movement direction limiting unit 504 is added to the input event processing unit 11 of the client device 1.

  The cursor position change check unit 231 determines whether or not the cursor position has changed before and after execution as a result of the input event being executed by the input event execution unit 223.

  The cursor movement direction determination unit 501 determines the movement direction of the mouse cursor when the cursor position changes before and after execution. When the cursor movement direction determination unit 501 determines that the movement direction of the mouse cursor has moved only in the X-axis direction, the cursor movement direction determination unit 501 determines the X-axis direction as a limited direction of cursor movement. If the cursor movement direction determination unit 501 determines that the movement direction of the mouse cursor has moved only in the Y-axis direction, the cursor movement direction determination unit 501 determines the Y-axis direction as a limited direction of cursor movement.

  The cursor movement direction notifying unit 502 notifies the client device 1C of the limited direction of cursor movement determined by the cursor movement direction determining unit 501.

  The cursor position history check unit 232 checks whether or not the position of the cursor that has changed before and after execution is held in the input event history holding unit 21. Here, when the limited direction of cursor movement is determined, the cursor position history check unit 232 checks only in the determined limited direction. For example, when the limited direction of cursor movement is the X-axis direction, the cursor position history check unit 232 determines that the X-axis coordinate of the mouse cursor that has changed is the coordinate of any X-axis of the input event history holding unit 21. It is determined whether or not they match.

  When the cursor position history check unit 232 determines that the position of the cursor that has changed is held in the input event history holding unit 21, the cursor position history check unit 232 deletes the history before the input event history determined to be held. On the other hand, when the cursor position history check unit 232 determines that the changed mouse cursor position is not held in the input event history holding unit 21, the cursor position history check unit 232 indicates the changed mouse cursor position as the cursor position correction information transmission unit. 233 is notified.

  The cursor movement direction reception unit 503 receives a limited direction of cursor movement from the server device 2C. The cursor movement direction limiting unit 504 limits the movement direction of the mouse cursor on the device side to the limited direction of cursor movement received by the cursor movement direction reception unit 503.

[Specific example of cursor position correction]
Next, a specific example of cursor position correction will be described with reference to FIG. FIG. 18 is a diagram illustrating a specific example of cursor position correction according to the fourth embodiment. It is assumed that the area where the mouse cursor can move on the desktop screen of the server device 2C is the coordinate position “100” or more (downward here) on the Y axis. That is, in the example of FIG. 18, when the mouse cursor moves below the Y-axis coordinate position “100” (upward here) on the desktop screen of the client apparatus 1 </ b> C, the Y-axis coordinate position “100” is corrected. Shall.

  As illustrated in FIG. 18, when the client apparatus 1C acquires an input event in which the mouse destination is P1 ′ (205, 95) (not shown), the local echo is performed, and then the server apparatus 2C performs the Y-axis value. Is redrawn at the corrected position P1 (205, 100).

  Next, the input event acquisition unit 111 acquires an input event in which the mouse destination is P2 (210, 100) (step S1). The input event acquisition unit 111 passes the acquired input event to the input event transmission unit 112 and the cursor movement direction limiting unit 504. When the movement direction of the mouse cursor is limited, the cursor movement direction limiting unit 504 limits the movement direction of the mouse cursor for the input event that has been handed over. Then, the cursor drawing unit 113 performs local echo with coordinates moved only in a limited movement direction from the immediately preceding coordinates. On the other hand, when the moving direction of the mouse cursor is not limited, the cursor movement direction limiting unit 504 draws the cursor at the coordinates of the input event via the cursor drawing unit 113. At the same time, the input event transmitting unit 112 transmits the delivered input event as it is to the server device 2C (step S2C). Here, since the moving direction of the mouse cursor is not limited, the cursor drawing unit 113 draws the cursor as it is at the position of P2 (210, 100).

  In the server device 2, the input event receiving unit 221 receives the input event transmitted from the client device 1C. Then, the input event storage unit 222 holds the input event received by the input event reception unit 221 as an event history. Here, the input event storage unit 222 holds the coordinate P2 of the movement destination included in the input event as an event history. In addition, the input event execution unit 223 causes the OS 20 to process the input event received by the input event reception unit 221 (step S3).

  Then, the cursor position change check unit 231 acquires the coordinates of the mouse cursor that is the result of processing performed by the OS 20 (step S4). The cursor movement direction determination unit 501 determines the limited direction of mouse cursor movement because the acquired mouse cursor coordinates do not match the coordinates of the mouse cursor before processing, that is, the mouse cursor has moved (step S5C). ). Here, since the previous coordinates are (205, 100) and the current coordinates are (210, 100), the cursor movement direction determination unit 501 determines the X-axis direction as the cursor movement limited direction. Therefore, the cursor movement direction determination unit 501 notifies the client device 1C of the limited direction (X axis) of cursor movement via the cursor movement direction notification unit 502 (step S6C).

  Then, the cursor position history check unit 232 determines whether or not the coordinate P2 of the processed mouse cursor is held as the input event history, using the determined limited direction of cursor movement (step S7C). Here, since the determined limited direction of cursor movement is the X-axis direction, the coordinate value “210” of the X-axis among the coordinates P2 of the mouse cursor after processing is held as the input event history, so the coordinate P2 The previous history is deleted (step S8C). As described above, in the case of an input event in which the movement destination of the mouse is the coordinate P2, the coordinate P2 of the processed mouse cursor is not automatically changed by the OS 20, and thus the coordinates of the client device 1C are not corrected. Thus, the process is terminated. Note that the cursor position history check unit 232 stores the coordinates of the mouse cursor after processing in the client device 1C when the coordinate value of the limited direction of cursor movement among the coordinates of the mouse cursor after processing is not held as the input event history. Transmit (step S9C).

  In the client device 1C, the input event acquisition unit 111 acquires the next input event (step S1). Here, it is assumed that an input event in which the mouse destination is P3 ′ (215, 95), for example, is acquired. The input event acquisition unit 111 passes the acquired input event to the input event transmission unit 112 and the cursor movement direction limiting unit 504. The cursor movement direction limiting unit 504 limits the X axis direction, which is the movement direction of the mouse cursor, for the input event that has been handed over because the movement direction of the mouse cursor is limited to the X axis direction. Then, the cursor drawing unit 113 performs local echo at the coordinates P3 (215, 100) moved only in the limited X-axis direction from the immediately preceding coordinates P2. At the same time, the input event transmitting unit 112 transmits the delivered input event as it is to the server device 2C (step S2C).

  Thereafter, the server device 2C and the client device 1C continue to process the input event that has occurred on the client device 1C side. In this way, even when the movement area of the mouse cursor is limited on the server apparatus 2C side, the server apparatus 2C can prevent the movement locus of the mouse cursor of the client apparatus 1C from becoming unnatural.

[Input event processing procedure in client device]
Next, the procedure of input event processing in the client device 1C will be described with reference to FIG. FIG. 19 is a flowchart illustrating a procedure of input event processing in the client device according to the fourth embodiment. In addition, the same code | symbol is shown about the process same as the input event process in the client apparatus based on Example 1 shown in FIG.

  First, the input event acquisition unit 111 determines whether there is an unprocessed input event (step S11). When it is determined that there is no unprocessed input event (step S11; No), the input event acquisition unit 111 repeats the determination process until it is determined that there is an unprocessed input event. On the other hand, when it is determined that there is an unprocessed input event (step S11; Yes), the input event acquisition unit 111 acquires the input event (step S12).

  Subsequently, the cursor movement direction limiting unit 504 determines whether or not the movement direction of the mouse cursor is limited (step S81). When it is determined that the moving direction of the mouse cursor is limited (step S81; Yes), the cursor moving direction limiting unit 504 calculates the coordinates of the mouse cursor from the moving direction being limited and the input event (step S82). On the other hand, when it is determined that the moving direction of the mouse cursor is not limited (step S81; No), the cursor moving direction limiting unit 504 extracts the coordinates of the mouse cursor from the input event (step S83).

  Then, the cursor drawing unit 113 redraws the mouse cursor on the desktop screen of its own device based on the calculated or extracted coordinates of the mouse cursor (step S13).

  Then, the input event transmission unit 112 transmits the input event acquired by the input event acquisition unit 111 to the server device 2 as it is (step S14). Then, the input event processing unit 11 proceeds to step S11 in order to wait for the next event to occur.

[Procedure for cursor movement direction restriction processing in client device]
Next, the procedure of the cursor movement direction limiting process in the client device 1C will be described with reference to FIG. FIG. 20 is a flowchart illustrating the procedure of the cursor movement direction limiting process in the client device according to the fourth embodiment.

  First, the cursor movement direction receiving unit 503 determines whether or not a notification regarding the cursor movement direction has been received from the server device 2C (step S91). When it determines with not receiving the notification regarding a cursor movement direction (step S91; No), the cursor movement direction receiving part 503 repeats a determination process until the said notification is received.

  On the other hand, when it determines with having received the notification regarding a cursor movement direction (step S91; Yes), the cursor movement direction receiving part 503 receives the notification regarding the movement direction of a mouse cursor (step S92).

  Here, it is determined whether the cursor movement direction receiving unit 503 has received a notification regarding the limited direction of mouse cursor movement (step S93). When it is determined that the limited direction notification of mouse cursor movement has been received (step S93; Yes), the cursor movement direction limiting unit 504 controls to limit the moving direction of the mouse cursor on the client side (step S94). Then, the cursor movement direction limiting processing unit 50 proceeds to step S91 to wait for a notification regarding the next cursor movement direction.

  On the other hand, when it is determined that a notification regarding the limited direction of mouse cursor movement has not been received (step S93; No), the cursor movement direction receiving unit 503 determines whether or not a limited release notification of mouse cursor movement has been received. (Step S95). When it is determined that the mouse cursor movement limitation release notification has not been received (step S95; No), the cursor movement direction limitation processing unit 50 proceeds to step S91 in order to wait for a notification regarding the next cursor movement direction.

  On the other hand, when it is determined that the mouse cursor movement limitation release notification has been received (step S95; Yes), the cursor movement direction limiting unit 504 performs control so as not to limit the movement direction of the mouse cursor on the client side (step S96). ). Then, the cursor movement direction limiting processing unit 50 proceeds to step S91 to wait for a notification regarding the next cursor movement direction.

[Procedure for cursor position correction processing in server device]
Next, the procedure of the cursor position correction process in the server device 2C will be described with reference to FIG. FIG. 21 is a flowchart illustrating the procedure of the cursor position correction process in the server apparatus according to the fourth embodiment. In addition, the same code | symbol is shown about the process same as the cursor position correction process in the server apparatus based on Example 1 shown in FIG.

  The cursor position change checking unit 231 determines whether or not a predetermined time has elapsed (step S41). When it is determined that the predetermined time has not elapsed (step S41; No), the cursor position change check unit 231 repeats the determination process until the predetermined time has elapsed.

  On the other hand, when it is determined that a predetermined time has elapsed (step S41; Yes), the cursor position change check unit 231 checks whether or not the mouse cursor has moved (step S42).

  If it is determined that the mouse cursor has not moved (step S42; No), the cursor position correction unit 23 ends the cursor position correction process and proceeds to a screen information transfer process. On the other hand, when it is determined that the mouse cursor has moved (step S42; Yes), the cursor movement direction determination unit 501 determines the direction in which the mouse cursor has moved (step S101). Here, the cursor movement direction determination unit 501 determines whether or not the mouse cursor has moved only in the X-axis direction (step S102).

  When it is determined that the mouse cursor has moved only in the X-axis direction (step S102; Yes), the cursor movement direction determination unit 501 has notified the limited direction (X-axis direction) of the mouse cursor movement at least once. Is determined (step S103). If it is determined that the notification has been made once or more (step S103; Yes), the cursor movement direction determination unit 501 determines that the notification is unnecessary, and proceeds to step S110. On the other hand, when it is determined that the notification has not been made once or more (step S103; No), the cursor movement direction notifying unit 502 notifies the client apparatus 1C of the X axis direction as the limited direction of cursor movement (step S104), and step S110. Migrate to

  On the other hand, when it is determined that the mouse cursor has not moved only in the X-axis direction (step S102; No), the cursor movement direction determination unit 501 determines whether or not the mouse cursor has moved only in the Y-axis direction ( Step S105).

  When it is determined that the mouse cursor has moved only in the Y-axis direction (step S105; Yes), the cursor movement direction determination unit 501 has notified the limited direction (Y-axis direction) of the mouse cursor movement at least once. Is determined (step S106). When it is determined that the notification has been made once or more (step S106; Yes), the cursor movement direction determination unit 501 determines that the notification is unnecessary, and proceeds to step S110. On the other hand, when it is determined that the notification has not been made once or more (step S106; No), the cursor movement direction notifying unit 502 notifies the client apparatus 1C of the Y-axis direction as the cursor movement limited direction (step S107), and step S110. Migrate to

  On the other hand, when it is determined that the mouse cursor has not moved only in the Y-axis direction (step S105; No), the cursor movement direction determination unit 501 determines whether or not the restriction release of the movement direction of the mouse cursor has been notified. (Step S108). If it is determined that the restriction release of the movement direction of the mouse cursor has been notified (step S108; Yes), the cursor movement direction determination unit 501 determines that notification is not necessary, and proceeds to step S110. On the other hand, when it is determined that the restriction release of the movement direction of the mouse cursor has not been notified (step S108; No), the cursor movement direction notification unit 502 notifies the client device 1C of the restriction release of the cursor movement (step S109). The process proceeds to step S110.

  The cursor position history check unit 232 determines whether there is an input event corresponding to the position of the mouse cursor after movement (step S110). For example, the cursor position history check unit 232 determines whether or not the position of the mouse cursor that has changed matches any of the coordinate positions held as the input event history in the input event history holding unit 21. . At this time, if the cursor movement direction is being limited, the cursor position history check unit 232 only needs to check the coordinate values in the limited coordinate axis direction.

  If it is determined that the corresponding input event exists (step S110; Yes), the cursor position history check unit 232 deletes the history before the history of the corresponding input event (step S44). Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

  On the other hand, when it is determined that there is no corresponding input event (step S110; No), the cursor position history check unit 232 determines that the cursor position has been automatically changed by the OS 20. Then, the cursor position history check unit 232 causes the cursor position correction information transmission unit 233 to transmit the cursor position correction information to the client device 1C (step S45). Then, the cursor position correcting unit 23 ends the cursor position correcting process and proceeds to the screen information transfer process.

[Effect of Example 4]
According to the fourth embodiment, when the server apparatus 2C of the thin client system 9 performs processing based on the input event and the cursor position changes before and after processing, the cursor position before and after processing is one axis. It is determined whether or not only the direction has changed. If the server apparatus 2C determines that there is a change in only one axial direction, the position of the cursor that has changed in the changed axial direction is held in the input event history holding unit 21. It is determined whether or not it coincides with the cursor position. According to such a configuration, the server apparatus 2C reduces the cost of the comparison process by using the cursor position in the axial direction in which the comparison with the cursor position held in the input event history holding unit 21 has changed. can do.

  Further, when it is determined that there is a change in only one axial direction, the server apparatus 2C notifies the client apparatus 1C that the movement of the cursor is limited to the changed axial direction. According to such a configuration, the server device 2C can control the cursor movement trajectory in the client device 1C to be a natural movement even if the cursor movement region is limited.

[Programs]
In the first to fourth embodiments, the case where the cursor position is automatically changed by the OS 20 before and after the processing of the input event has been described. However, the present invention is not limited to this, and a driver or application software may be used instead of the OS 20, and any software or hardware may be used as long as the cursor position is automatically changed before and after the input event processing.

  In addition, the server device 2 is equipped with functions such as the input event processing unit 22, the cursor position correction unit 23, and the screen information transfer unit 24 in an information processing apparatus such as a known personal computer or workstation. Can be realized. In addition, the client device 1 can be realized by mounting each function such as the input event processing unit 11 and the screen drawing unit 12 on an information processing apparatus such as a known personal computer or workstation.

  In addition, each component of each illustrated apparatus does not necessarily need to be physically configured as illustrated. That is, the specific mode of distribution / integration of each device is not limited to that shown in the figure, and all or a part thereof may be functionally or physically distributed or arbitrarily distributed in arbitrary units according to various loads or usage conditions. Can be integrated and configured. For example, the cursor position change check unit 231 and the cursor position history check unit 232 may be integrated as one unit. On the other hand, the cursor position history check unit 232 may be distributed to a determination unit that determines whether or not the cursor position is held in the history, a deletion unit that deletes the history when held, and the like. . Further, a storage unit such as the input event history holding unit 21 may be connected as an external device of the server device 2 via a network.

  The various processes described in the above embodiments can be realized by executing a program prepared in advance on a computer such as a personal computer or a workstation. Therefore, in the following, an example of a computer that executes a cursor position correction program that realizes the same function as the server device 2 illustrated in FIG. 1 will be described. FIG. 22 is a diagram illustrating an example of a computer that executes a cursor position correction program.

  As illustrated in FIG. 22, the computer 200 includes a CPU 201 that executes various arithmetic processes, an input device 202 that receives input of data from a user, and a display 203. The computer 200 also includes a reading device 204 that reads a program and the like from a storage medium, and an interface device 205 that exchanges data with other computers via a network. The computer 200 also includes a RAM 206 that temporarily stores various information and a hard disk device 207. The devices 201 to 207 are connected to the bus 208.

  The hard disk device 207 stores a cursor position correction program 207a and cursor position correction related information 207b. The CPU 201 reads the cursor position correction program 207 a and develops it in the RAM 206. The cursor position correction program 207a functions as a cursor position correction process 206a.

  For example, the cursor position correction process 206a corresponds to the input event processing unit 22, the cursor position correction unit 23, and the screen information transfer unit 24. The cursor position correction related information 207 b corresponds to the input event history holding unit 21.

  The cursor position correction program 207a does not necessarily have to be stored in the hard disk device 207 from the beginning. For example, the program is stored in a “portable physical medium” such as a flexible disk (FD), a CD-ROM, a DVD disk, a magneto-optical disk, or an IC card inserted into the computer 200. Then, the computer 200 may read out and execute the cursor position correction program 207a from these.

1 Client device 10, 20 OS
DESCRIPTION OF SYMBOLS 11 Input event process part 12 Screen drawing part 111 Input event acquisition part 112 Input event transmission part 113 Cursor drawing part 121 Cursor position correction information receiving part 122 Cursor position correction part 123 Screen information receiving part 124 Image expansion process part 125 Screen information drawing part 2 Server device 21 Input event history holding unit 22 Input event processing unit 23 Cursor position correction unit 24 Screen information transfer unit 221 Input event reception unit 222 Input event storage unit 223 Input event execution unit 231 Cursor position change check unit 232 Cursor position history check 233 Cursor position correction information transmission unit 241 Screen information acquisition unit 242 Screen update determination unit 243 Image compression processing unit 244 Screen information transmission unit

Claims (8)

A pointer position correction method executed by a server,
Received from the client the event information including the event accompanied by the movement of the pointer and the position of the pointer after the movement, which is input by the client connected to the server via the network, and stores the received event information in the event history,
As a result of processing based on the event information, when the position of the pointer has changed before and after the processing, the position of the pointer that has changed matches the position of the pointer of any event information stored in the event history. Determine whether or not
As a result of the determination process, when it is determined that the position of the pointer that has changed does not match the position of the pointer of any event information stored in the event history, the pointer of the pointer that has changed A pointer position correction method for notifying the client of the position and executing each process. As a result of the determination process, when it is determined that the position of the pointer that has changed corresponds to the position of the pointer of any event information stored in the event history, the position of the matched pointer is included. The pointer position correcting method according to claim 1, wherein the server further executes a process of deleting event information and event information received before the event information. As a result of the determination process, when it is determined that the position of the pointer that has changed matches the position of the pointer of any event information stored in the event history, the matched event information and The server executes a process of setting a processing interval based on the event to be larger than a current processing interval when the number of event information received before the event information is larger than a threshold value. The pointer position correction method described in 1. The server further executes a process of notifying the client of the changed pointer shape when the pointer shape changes before and after the processing as a result of processing based on the event. The pointer position correction method according to any one of claims 1 to 3. As a result of processing based on the event, when the position of the pointer has changed before and after processing, the position of the pointer before and after processing changes only in one of the coordinate axes representing the position. If it is determined whether or not there is a change in only one axial direction, the position of the pointer that has changed in the changed axial direction is stored in the event history. The pointer position correcting method according to any one of claims 1 to 4, wherein the server executes a process of determining whether or not the position of the pointer matches the position of the pointer. In the determination process, when it is determined that there is a change in only one axial direction, the server further executes a process of notifying the client that the movement of the pointer is limited to the changed axial direction. The pointer position correcting method according to claim 5, wherein On the server,
Received from the client the event information including the event accompanied by the movement of the pointer and the position of the pointer after the movement, which is input by the client connected to the server via the network, and stores the received event information in the event history,
As a result of processing based on the event information, when the position of the pointer has changed before and after the processing, the position of the pointer that has changed matches the position of the pointer of any event information stored in the event history. Determine whether or not
As a result of the determination process, when it is determined that the position of the pointer that has changed does not match the position of the pointer of any event information stored in the event history, the pointer of the pointer that has changed A pointer position correction program for executing each process for notifying the client of a position. A storage unit for storing event information including an event involving movement of the pointer and a position of the pointer after the movement;
A storage unit that receives event information of the event input from a client connected to the own device via a network from the client, and stores the received event information in the storage unit;
As a result of processing based on the event information, when the position of the pointer has changed before and after the processing, the position of the pointer that has changed matches the position of the pointer of any event information stored in the storage unit. A determination unit for determining whether or not
As a result of determination by the determination unit, when it is determined that the position of the pointer that has changed does not match the position of the pointer of any event information stored in the storage unit, the pointer that has changed And a notification unit for notifying the client of the location of the server.

Images