Display program and display method

Abstract

To provide a display program and a display method that improve than ever, user convenience when checking a process through which an object displayed on a display unit was edited to become a current object.SOLUTION: According to a display program, a control unit of a computer performs the steps of: in response to acquisition of an editing instruction (S8:YES), storing history information in which an object, an edit content of the object, and sequence information indicating editing sequence are associated with each other (S10); in response to acquisition of an editing instruction (S8:YES), updating the object displayed in a display unit (S9); acquiring a target period specification condition (S6); and identifying, as a target object, an object corresponding to the history information in the target period specified in the condition among one or more objects displayed on the display unit, and highlighting the identified target object (S7).SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present invention relates to a display program and a display method.

Background Art

[0002] Conventional collaborative work support systems can contact users of drawing information in a created file or object users in a general document using any communication means (for example, see Patent Document 1). Specifically, the system stores contact information of a user in at least one type of communication medium corresponding to the identification information of the user of the drawing information. The system displays the identification information of the user of the drawing information corresponding to the drawing information, and receives an instruction from the user to contact the user corresponding to the drawing information. The system acquires the contact information of the user in the communication medium, and connects the user's computer and the user's contact via the communication medium according to the acquired contact information.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] In a conventional collaborative work support system, it is difficult to confirm through what process the object displayed on the display unit was edited into the current object.

[0005] An object of the present invention is to provide a display program and a display method that improve the convenience of a user when confirming through what process the object displayed on the display unit was edited into the current object, as compared with the prior art.

Means for Solving the Problems

[0006] A display program according to a first aspect of the present invention includes an instruction to the control unit of a computer comprising a display unit and a control unit to execute the following steps: a history storage step of storing history information relating an object, the content of the editing of the object, and order information representing the editing order, in response to receiving an editing instruction to edit an object; a display control step of updating the object displayed on the display unit in response to receiving the editing instruction; a condition acquisition step of acquiring a condition for specifying a target period among the total period for which a plurality of the history information is stored; an identification step of identifying one or more of the objects displayed on the display unit that corresponds to the history information within the target period specified by the condition among the plurality of history information as a target object; and a highlighting step of highlighting the identified target object. A computer executing the display program according to the first aspect contributes to making it easier for the user to distinguish between a target object edited during the target period and other objects among one or more objects displayed on the display unit by highlighting the target object on the display unit. Therefore, the highlighting step of the display program contributes to improving the user's convenience when checking how an object displayed on the display unit was edited to become the current object compared to conventional methods.

[0007] A second aspect of the present invention relates to a display method performed by the control unit of a computer comprising a display unit and a control unit, and includes: a history storage step of storing history information relating an object, the content of the edited object, and sequence information representing the editing order, in response to receiving an editing instruction to edit an object; a display control step of updating the object displayed on the display unit in response to receiving the editing instruction; a condition acquisition step of acquiring a condition for specifying a target period among the total period for which a plurality of the history information is stored; a specification step of identifying one or more of the objects displayed on the display unit as a target object, which corresponds to the history information within the target period specified by the condition among the plurality of the history information; and a highlighting step of highlighting the identified target object. The display method relating to the second aspect contributes to making it easier for the user to distinguish between a target object edited during the target period and other objects among one or more objects displayed on the display unit by highlighting the target object on the display unit. Therefore, the highlighting step of the display method contributes to improving the user's convenience when checking how an object displayed on the display unit was edited to become the current object compared to conventional methods. [Brief explanation of the drawing]

[0008] [Figure 1] This diagram shows the electrical configuration of editing system 1. [Figure 2] This is a flowchart of the main process. [Figure 3] These are explanatory diagrams for the specific example screens G1 and G2. [Figure 4] This is an explanatory diagram of the history information storage area 39. [Figure 5] This is a flowchart of the notification display process. [Figure 6]This diagram illustrates the screen transitions of the display unit 35 on terminal device 3A of user A, the display unit 35 on terminal device 3B of user B, and the display unit 35 on terminal device 3C of user C in a specific example. [Figure 7] This diagram illustrates the screen transitions of the display unit 35 on terminal device 3A of user A, the display unit 35 on terminal device 3B of user B, and the display unit 35 on terminal device 3C of user C in a specific example. [Figure 8] This is a flowchart of the notification transmission process for the first modified example. [Figure 9] This is a flowchart of the notification display process for the first modified example. [Figure 10] This is a flowchart of the notification display process for the second modified example. [Modes for carrying out the invention]

[0009] Embodiments of this disclosure will be described with reference to the drawings. As shown in Figure 1, the editing system 1 has a server 2 and three terminal devices 3. The server 2 is connected to an access point 5 via a network line 4 so as to be communicative. The three terminal devices 3 are each used by different users A, B, and C. Each terminal device 3 is a portable terminal device such as a well-known tablet terminal device and a multifunction mobile phone (so-called smartphone), and is connected to the access point 5 so as to be wireless. Hereinafter, the terminal device 3 used by user A will also be called terminal device 3A, the terminal device 3 used by user B will also be called terminal device 3B, and the terminal device 3 used by user C will also be called terminal device 3C. In the following description, for the sake of simplicity, the case in which terminal devices 3A to 3C each have the same configuration will be described, but terminal devices 3A to 3C may each have different configurations.

[0010] As shown in Figure 1, Server 2 has a CPU 6, ROM 21, RAM 22, flash memory 23, and a communication unit 24. The CPU 6 controls Server 2. ROM 21 stores information that the CPU 6 needs when executing various programs. RAM 22 temporarily stores data during the process of the CPU 6 executing processing. Flash memory 23 is a non-volatile storage device. Flash memory 23 includes a program storage area 25, an account storage area 26, a display information storage area 27, and a history information storage area 28. The program storage area 25 stores various programs executed by the CPU 6. The account storage area 26 stores account information. Account information includes user information to distinguish one user from other users, and a password used when logging into the editing system 1. The display information storage area 27 stores display information indicating the object displayed in the latest editing area 71 (see Figure 3). The history information storage area 28 stores the history information described later. The communication unit 24 is a communication module that allows the server 2 to communicate with each of the terminal devices 3A through 3C via the network line 4 and the access point 5.

[0011] The terminal device 3 comprises a CPU 7, ROM 32, RAM 33, flash memory 34, display unit 35, input unit 36, and communication unit 37. The CPU 7 controls the terminal device 3. The ROM 32 stores information required by the CPU 7 when executing various programs. The RAM 33 temporarily stores data during the process of the CPU 7 executing processing. The flash memory 34 stores various programs, including the display program described later, which are executed by the CPU 7. The display unit 35 is a liquid crystal display capable of displaying various information. The input unit 36 ​​is provided on the surface of the display unit 35 and detects the contact position of an operating object such as a pen or finger on the display unit 35, and outputs a detection signal to the CPU 7 according to the detected contact position. The communication unit 37 is a communication module for the terminal device 3 to communicate with the server 2 via the network line 4 and access point 5.

[0012] As shown in Figure 1, the editing system 1 allows multiple users A through C to use their respective terminal devices 3A through 3C to edit objects in a common editing area 71, as described later with reference to Figure 3, simultaneously or at different times via the server 2. Users operate terminal device 3 to launch a shared application. Upon launching the shared application, the editing system 1 can display the screen shared among the terminal devices 3 specified by the users on the display unit 35 of each terminal device 3.

[0013] The following describes the process performed by the editing system 1, using the case where an editing operation is performed on terminal device 3A as an example. When the CPU 7 of terminal device 3A detects editing of an object via the input unit 36, the CPU 7 of terminal device 3A updates the screen of the display unit 35 according to the editing content. The CPU 7 of terminal device 3A sends history information corresponding to the editing content to the server 2 via the network line 4 and access point 5, and stores the history information in the history information storage area 39 of terminal device 3A. When the CPU 6 of server 2 receives the history information from terminal device 3A, it stores the received history information in the history information storage area 28 and updates the display information storage area 27 according to the history information. The CPU 6 sends the display information and history information to other terminal devices 3 that perform editing of the editing area 71 together with terminal device 3A via the network line 4 and access point 5. When terminal devices 3B and 3C receive the display information and history information, the CPU 7 of terminal devices 3B and 3C, according to the received display information and history information, 、3C The display unit 35 is updated. As a result, the contents of the editing area 71 are displayed on the display unit 35 of each terminal device 3A, 3B, and 3C, and are shared within the editing system 1.

[0014] Referring to Figures 2 to 7, the main processing performed in each of the terminal devices 3A to 3C will be explained. The main processing of terminal devices 3A to 3C is performed individually in each terminal device 3, but for the sake of simplicity, it will be explained in parallel. When the CPU 7 detects a login instruction to log in to the editing system 1 entered by the user via the input unit 36, it reads the display program from the program storage area 38 shown in Figure 1. The CPU 7 starts the main processing shown in Figure 2 by executing the read display program. As an example, a specific example is used in which users A through C jointly edit a zoo layout proposed by user A using the editing system 1. In this specific example, the editing area 71 is edited or viewed by users A through C. The period during which the editing area 71 is edited and viewed spans multiple days, and the periods during which each user edits and views the editing area 71 overlap to some extent.

[0015] As shown in Figure 2, the CPU 7 of each terminal device 3 performs login processing to log in to the editing system 1 (S1). Specifically, the CPU 7 sends login information, including user information and password included in the login instruction, to the server 2. The CPU 6 of the server 2 compares the received login information with the account information stored in the account storage area 26. If the login is successful, the CPU 6 sends the display information and history information of the editing area 71 to be edited, which is associated with the terminal device 3 that performed the login processing, to the terminal device 3 that performed the login processing, and continues the subsequent processing. If the display information associated with the terminal device 3 is not stored in the display information storage area 27, the CPU 6 of the server 2 performs processing to start editing the editing area 71 anew. If the login fails, the CPU 6 sends error information to the terminal device 3 that performed the login processing and cancels the subsequent processing. The CPU 6 is configured to be able to identify the terminal device 3 that sent the history information based on the login information, even when multiple users are logged into the editing system 1 simultaneously. The CPU 7 of the terminal device 3, which has received display information and history information from the server 2, displays the editing screen 70 shown in Figure 3 on the display unit 35.

[0016] As shown in FIG. 3, the editing screen 70 includes an editing area 71, a button display area 72, a history button 73, a checkpoint button 75, and a display area 74. The editing area 71 is an area where an object can be edited. In the initial state of the editing area 71, no object is placed. An object is placed in the editing area 71 according to an editing operation of a user of any one of the terminal devices 3. In the example shown in FIG. 3, the editing area 71 includes objects J1 to J6. The objects J1 to J6 represent an arrangement plan of the lion area, the tiger area, and the pond in the zoo edited by the user A. The object J1 is the character "LION", and the object J2 is a rectangle surrounding the object J1. The object J3 is the character "TIGER" placed below the objects J1 and J2, and the object J4 is a rectangle surrounding the object J3. The object J5 is the character "POND", and the object J6 is a circle surrounding the object J5 and placed to the left of the objects J1 to J4.

[0017] The button display area 72 displays a plurality of buttons 81 to 89 that are selected when specifying an editing attribute indicating the type of the object to be edited in the editing area 71 or the editing content. The editing attributes of the present embodiment include a stroke, a marker, characters, a figure, and an image. The stroke is a line such as a straight line and a curve extending to a position indicated by a detection signal. The marker is a line having a predetermined width for coloring. The characters are characters, numbers, symbols, etc. arranged in a rectangular character block (not shown). The figure is a planar figure or a three-dimensional figure. The image is a still image or a moving image. The editing content of the present embodiment includes addition, deletion, movement, color change, size change, font change, etc. of an object.

[0018] Button 81 is selected when adding a stroke. Button 82 is selected when deleting an object. Button 83 is selected when adding a marker. Button 84 is selected when adding text. Button 85 is selected when adding a graphic. Button 86 is selected when adding an image. Button 87 is selected when changing the color of an object. Button 88 is selected when changing the thickness of a stroke. Button 89 is selected when sending a notification to other users who co-edit the editing area 71.

[0019] The history button 73 and the checkpoint button 75 are selected when switching between displaying a list of history information or a list of checkpoints in the display area 74 on the editing screen 70. A checkpoint is information used to specify a partial target period out of the entire period in which a plurality of history information is stored in the history information storage area 39. The checkpoint of the present embodiment is automatically generated and stored in the history information storage area 39 in response to the transmission of a notification. The screen G1 in FIG. 3 shows a state where the history button 73 is selected and a list of history information is displayed in the display area 74, and the screen G2 in FIG. 3 shows a state where the checkpoint button 75 is selected and a list of checkpoints is displayed in the display area 74. When the checkpoint button 75 is selected, a selection bar 76 is displayed at the upper part of the display area 74. The selection bar 76 is selected when extracting and displaying checkpoints that meet specific conditions from the list of checkpoints displayed in the display area 74. The specific condition of the present embodiment is the user who performed the operation of generating the checkpoint.

[0020] The CPU 7 determines whether a notification instruction to send a notification has been detected based on whether button 89 has been selected (S2). If no notification instruction has been detected (S2:NO), the CPU 7 determines whether a notification has been received from another terminal device 3 or whether an instruction to select a notification has been detected (S6). The CPU 7 determines that an instruction to select a notification has been detected if an operation in which any of the checkpoints displayed in the display area 74 has been selected is detected. If no notification has been received from another terminal device 3 and no instruction to select a notification has been detected (S6:NO), the CPU 7 determines whether an edit instruction has been detected (S8).

[0021] In terminal device 3A, if button 84 is selected while no object is placed in the editing area 71, and the text "LION" is entered (S8:YES), the CPU 7 of terminal device 3A updates the object to be displayed on the display unit 35 in response to receiving an editing instruction (S9). In response to receiving an editing instruction to edit object J1, the CPU 7 stores history information in the history information storage area 39, associating object J1, the content of the edits to object J1, and order information representing the editing order (S10). In this embodiment, history information is stored for each editing operation. In addition to the object, the content of the edits, and the order information, the CPU 7 in this embodiment stores user information identifying the user who performed the edits as history information in the history information storage area 39.

[0022] As shown in Figure 4, the history information indicates the history corresponding to the editing operation. In this embodiment, the history information includes a history ID 41, user information 42, editing date and time 43, editing position 44, editing attribute / object 45, editing content 46, and notification 47. The history ID 41 is the identification information for the history information. In this embodiment, the history ID 41 is a string combining the letter R and a number indicating the memory order. In the following description, the history ID 41 is used to identify the history information. For example, history information R1 indicates the history information where the history ID 41 is "R1".

[0023] User information 42 can be any information that can identify the user using terminal device 3, and may be the user's name or the identification information of terminal device 3. In this embodiment, user information 42 is the username, and CPU 7 sets the user information in history information R1 to "User A," indicating that the editing operation was performed by user A. Edit date and time 43 indicates a representative point in time when an editing operation was performed, and in this embodiment, the representative point in time indicates the time when the editing operation was completed. CPU 7 sets the editing date and time in history information R1 to "July 1, 2022 W1," the date and time when the editing operation was completed. In Figure 4, the string of characters, such as W1, which combines the letter W and a number indicating the memory order, is simplified time information for the sake of explanation. The order information included in the history information in this embodiment is the editing date and time 43.

[0024] The editing position 44 indicates the position of a representative point within the editing area 71 (see Figure 3) of the object edited by the editing operation, using coordinate data. The origin of the coordinate data can be set as appropriate, for example, located at the upper left corner of the editing area 71. The left-right direction of the editing area 71 corresponds to the X-axis direction. The up-down direction of the editing area 71 corresponds to the Y-axis direction. The representative point is, for example, either the center or a vertex of the rectangle that encloses the object. The CPU 7 sets (X1, Y1) to the editing position 44 in the history information R1.

[0025] The Edit Attribute / Object 45 indicates the type and object of the object being edited. The CPU 7 sets the Edit Attribute / Object 45 of the History Information R1 to "Character (LION)". The Edit Content 46 indicates the edit made to the object. The CPU 7 sets the Edit Content 46 of the History Information R1 to "Add". The Notification 47 indicates the user information to which notifications will be sent between the CPU 7 and other terminal devices 3. If a checkpoint generated when button 89 is selected is stored, the CPU 7 sets the Notification 47 to the user information to which the notification will be sent. If history information is stored in response to an editing operation, the CPU 7 sets the Notification 47 to "-" to indicate that no notification has been sent.

[0026] The CPU 7 of terminal device 3A transmits history information R1 to server 2. The editing system 1 of this embodiment is configured to store history information in the history information storage area 28 for each editing area 71. In this embodiment, the history information stored in the history information storage area 28 and the history information stored in the history information storage area 39 are the same. When server 2 receives history information, it stores the history information R1 in the history information storage area 28 as history information for the editing area 71, and, in cooperation with terminal device 3A which transmitted the history information R1, transmits the history information R1 and display information to the currently logged-in terminal device 3 among the other terminal devices 3 that are editing the editing area 71. When the CPU 7 of terminal device 3B receives the history information R1 from server 2 for terminal device 3A, it determines that editing has been performed by user A based on the received history information R1 (S8: YES), and displays the content edited by user A on the display unit 35 based on the history information R1 and display information (S9). The CPU 7 of terminal device 3B stores the received history information (S10).

[0027] Through a similar process, the CPU 7 of terminal device 3A performs the editing of objects J2 to J6 (S8:YES, S9), and stores the history information R2 to R6 corresponding to each of objects J2 to J6 in the history information storage area 39 (S10).

[0028] If no edit instruction is detected (S8:NO), CPU7 determines whether a notification history instruction to display the notification history has been detected based on whether the checkpoint button 75 is selected (S11). If no notification history instruction is detected (S11:NO), CPU7 determines whether a sort instruction to select a user has been detected based on whether the selection field 76 is selected (S13). If no sort instruction is detected (S13:NO), CPU7 returns to processing S2.

[0029] If the CPU 7 of terminal device 3A detects a notification instruction (S2:YES), it generates a history ID 41 (S3). The CPU 7 acquires information identifying the notification recipient, the editing screen 70 currently displayed on the display unit 35, and the notification content. It then sends a notification containing the acquired information identifying the editing screen 70, the notification content, and the history ID generated in S3 to the acquired notification recipient (S4). The notification may be sent directly to the notification recipient terminal device 3, or it may be sent to the notification recipient terminal device 3 via the server 2. The CPU 7 stores the notification history as a checkpoint used to identify the target period, including sequence information (S5). In this embodiment, the CPU 7 stores sender information in the history information storage area 39, in addition to the notification date and time as sequence information. The CPU 7 sets the sender information "User A" in the user information 42 of the history information R7 and sets the notification date and time "2022 / 7 / 3 W7" in the editing date and time 43. CPU7 sets "-" to indicate that the object has not been edited for each of the editing position 44, editing attribute / object 45, and editing content 46 of the history information R7, and sets the recipient user information "User B, User C" for notification 47.

[0030] If object J8 is added to terminal device 3A after terminal device 3A has sent a notification, CPU 7 performs the process of editing object J8 (S8:YES, S9) and stores the history information R8 corresponding to object J8 in the history information storage area 39 (S10).

[0031] After object J8 is added to terminal device 3A, if terminal device 3B performs login processing based on a notification sent from terminal device 3A (S1), the CPU 7 of terminal device 3B obtains a condition that specifies a target period for a portion of the total period during which multiple history information is stored in the history information storage area 39 (S6: YES), and performs notification display processing (S7). The condition in this embodiment is a condition that targets a period within the total period during which multiple history information is stored, which is demarcated by a checkpoint specified by the history ID included in the notification or instruction in S6. The total period during which multiple history information is stored in the history information storage area 39 is the period from when the first history information is stored in the history information storage area 39 to when the last history information is stored in the history information storage area 39. The target period in this embodiment is the period demarcated by a checkpoint. More specifically, the conditions of this embodiment are that the end point of the target period is set to the point in time when the checkpoint identified by the history ID in S6 is stored, and the start point of the target period is set according to whether or not there is a checkpoint prior to the checkpoint identified by the history ID in S6.

[0032] As shown in Figure 5, the CPU 7 of terminal device 3B determines whether the notification display process was executed in response to receiving a notification from another terminal device 3 (S20). The CPU 7 of terminal device 3B determines that it is executing the notification display process in response to receiving a notification from terminal device 3A (S20: YES), stores the history information R7 corresponding to the notification in the history information storage area 39 (S21), and displays the screen associated with the notification (S22). The screen associated with the notification is a screen displayed based on information that identifies the editing screen 70 included in the notification, and is the editing screen 70 that terminal device 3A was displaying when user A, the sender, performed the notification operation.

[0033] If the notification display process has not been executed in response to receiving a notification from another terminal device 3 (S20: NO), or after S22, the CPU 7 determines whether the notification from the other terminal device 3, or the instruction to select a notification, obtained in the process of S6, includes a history ID (S23). The history ID is included in the condition that specifies a target period out of the total period over which multiple history information is stored. If the history ID is not included (S23: NO), the CPU 7 terminates the notification display process and returns to the main process S2. The CPU 7 may display an error message indicating that the history ID is not included.

[0034] The CPU 7 of terminal device 3B determines that the notification acquired in S6 contains "R7" as the history ID (S23: YES), searches for history information R7 in the history information storage area 39 (S24), and identifies the sender of the notification as "User A" (S25). The CPU 7 of terminal device 3B refers to the history information storage area 39 and searches whether there is a notification sent by User A, identified in S25, before history information R7 (S26), and determines whether there is a notification sent by User A before history information R7 (S27). In this embodiment, the CPU 7 changes the method of setting a target period for a part of the total period during which multiple history information is stored in the history information storage area 39, according to the condition for specifying the target period and the result of the determination in S27.

[0035] The CPU 7 of terminal device 3B determines that there were no notifications sent by user A before history information R7 (S27: NO). In this case, the CPU 7 of terminal device 3B selects the period before history information R7 as the target period T1 from among the multiple history information stored in the history information storage area 39, and extracts the history ID 41 of the history information stored in the target period T1 and in which user information 42 is user A (S29). The CPU 7 of terminal device 3B obtains R1 to R6 from the history ID 41 of the multiple history information stored in the history information storage area 39.

[0036] The CPU 7 identifies the object corresponding to the history information within the target period specified by the conditions among the multiple history information items as the target object from among the one or more objects displayed on the display unit 35 (S29). In this embodiment, the CPU 7 identifies the object corresponding to the history information that includes user information of the checkpoint, within the target period separated by the checkpoints specified by the conditions among the multiple history information items as the target object from among the one or more objects displayed on the display unit 35.

[0037] In a specific example, if it is determined that no notifications were sent by user A before history information R7 (S27: NO), the CPU 7 of terminal device 3B extracts history information R1 to R6 within the target period T1 (S29), and identifies the objects J1 to J6 that correspond to the history information R1 to R6 from which history ID 41 was extracted in the process of S29 as target objects among one or more objects J1 to J6 and J8 displayed on the display unit 35 (S30).

[0038] The CPU 7 of terminal device 3B highlights the target objects J1 to J6 identified in S30 (S31). The highlighting method may be selected as appropriate. Highlighting methods include blinking, changing the object's color, changing the object's background color, outlining the object, and shadowing the object. The highlighting method may be pre-set or set by the user. The highlighting method may be changed according to user information and object attributes.

[0039] As shown in screen F1 of Figure 6, the highlighting in this embodiment is a display mode in which a border of a different color from the object's color is added to the target object. The type of border, including at least one of the border color, the spacing from the object, and the thickness, may be pre-set or set by the user. The border does not need to encircle the object and may be applied only to a part of the object's perimeter. In screen F1, the borders added to target objects J1 to J6 are shown as a dotted shade. During the period in which target objects J1 to J6 are highlighted, the CPU 7 of the terminal device 3B also highlights the checkpoint history 97 displayed in the display area 74. The checkpoint history 97 shows the history information R7 corresponding to the notification acquired in S6.

[0040] CPU7 determines in S31 whether a predetermined time has elapsed since the highlighting started (S32). The predetermined time can be set as appropriate and may be a predetermined value or a value set by the user. If the predetermined time has not elapsed (S32: NO), CPU7 returns to processing in S32. If the predetermined time has elapsed (S32: YES), CPU7 of terminal device 3B removes the border applied to target objects J1 to J6, as shown in screen F2, and returns to normal display (S33). CPU7 of terminal device 3B also removes the highlighting of the checkpoint history 97 displayed in display area 74. With this, CPU7 of terminal device 3B finishes the notification display processing and returns to processing in main processing S2.

[0041] When object J9 is added on terminal device 3A, as shown in screen G4, the CPU 7 of terminal device 3A performs the editing process for object J9 (S8:YES, S9) and stores the history information R9 corresponding to object J9 in the history information storage area 39 (S10). The CPU 7 of terminal device 3B obtains the history information R9 and display information of object J9 via server 2 (S8:YES), performs the editing process for object J9 as shown in screen F3 (S8:YES, S9), and stores the history information R9 corresponding to object J9 in the history information storage area 39 (S10). In this way, when multiple users are editing the same editing area 71 simultaneously, if the process in S7 is not performed, the objects in the editing area 71 will not be highlighted even if the editing area 71 is updated in response to editing operations performed on other terminal devices 3.

[0042] After object J9 is added on terminal device 3A, object J10 is added on terminal device 3B. J When 16 is added in order, as shown in screen F4, the CPU 7 of terminal device 3B sequentially performs the editing of objects J10 to J16 (S8:YES, S9), and stores the history information R10 to R16 corresponding to each of objects J10 to J16 in the history information storage area 39 (S10). Object J10 is a square-shaped rectangle surrounding object J6, and object J11 is the word "SQUARE" placed above object J10. Object J12, J Object 15 is an arrow-shaped stroke, object J13 is a semicircular stroke surrounding objects J1 and J3, object J14 is a line segment extending horizontally between objects J1 and J3, and object J16 is the word "CHANGE" positioned above object J10.

[0043] The CPU 7 of terminal device 3A obtains history information R10 to R16 and display information for objects J10 to J16 via server 2 (S8:YES), performs editing of objects J10 to J16 as shown on screen G5 (S8:YES, S9), and stores the history information R10 to R16 corresponding to each of objects J10 to J16 in the history information storage area 39 (S10).

[0044] From object J10 on terminal device 3B J After 16 is added, if notifications are sent from terminal device 3B to user A and user C respectively, the CPU 7 of terminal device 3A acquires the notification (S6:YES), displays the screen associated with the notification (S20:YES, S21, S22), and identifies user B as the sender of the notification based on the history ID "R17" (S23:YES, S24, S25). Since there are no notifications sent by user B before history information R17 (S26, S27:NO), the CPU 7 of terminal device 3A identifies R10 to R16 as history IDs stored in the target period T3 prior to history information R17, where the user information is user B (S29). The CPU 7 of the terminal device 3A identifies objects J10 to J16, which correspond to the extracted R10 to R16, from among the objects J1 to J6 and J8 to J16 displayed on the display unit 35 as target objects (S30), highlights the target objects J10 to J16 for a predetermined time as shown in screen G6 (S31, S32), and removes the highlighting of the target objects J10 to J16 after the predetermined time has elapsed as shown in screen G7 in Figure 7 (S33).

[0045] After notifications are sent from terminal device 3B to users A and C, if objects J6 and J10 are deleted, objects J20 and J21 are added, objects J2 and J4 are deleted, and object J24 is added in terminal device 3A, then, as shown in screen G8, the CPU 7 of terminal device 3A performs the editing process for each object (S8:YES, S9) and stores the history information R18 to R24 corresponding to each object in the history information storage area 39 (S10). Object J20 is a square-shaped rectangle surrounding object J5, and objects J21 and J24 are the letters "OK".

[0046] When a notification containing the history ID "R25" is sent from terminal device 3A to users B and C (S6:YES), the CPU 7 of terminal device 3C performs notification display processing (S7). As shown in Figure 5, the CPU 7 of terminal device 3C acquires the notification (S6:YES), displays the screen associated with the notification (S20:YES, S21, S22), and then identifies user A who sent the notification based on the history ID "R25" (S23:YES, S24, S25). History information R7 is stored as a notification sent by user A before history information R25 (S26, S27:YES). In this case, the CPU 7 of terminal device 3C uses the period between the first checkpoint of the conditions acquired in S23 and the second checkpoint identified in S27 according to the first checkpoint as the target period.

[0047] The CPU 7 of terminal device 3C sets the history information R25 retrieved in S24 as the first checkpoint and the history information R7 acquired in S27 as the second checkpoint. If there are multiple checkpoints with the same user information as the first checkpoint that were stored before the first checkpoint, the CPU 7 sets the checkpoint closest to the first checkpoint as the second checkpoint. The CPU 7 of terminal device 3C sets the period between the first checkpoint and the second checkpoint identified according to the first checkpoint as the target period T2, and extracts R24 from R8, R9, and R18 as history IDs of history information that are within the target period T2 and contain the user information of the first checkpoint (S28).

[0048] The CPU 7 of terminal device 3C identifies objects J8, J9, J20, J21, and J24, which correspond to the extracted R8, R9, R18 to R24, from among the objects J1, J3, J5, J8, J9, J11 to J16, J20, J21, and J24 displayed on the display unit 35, as target objects (S30). As shown in screen E1, the CPU 7 of terminal device 3C highlights the target objects J8, J9, J20, J21, and J24 for a predetermined time (S31, S32), and as shown in screen E2, after the predetermined time has elapsed, the CPU 7 of terminal device 3C highlights the target objects J8, J9, J20, J21, and J24 of Remove the highlighting (S33).

[0049] After notifications are sent from terminal device 3A to users B and C, if user A is selected in the selection field 76 of terminal device 3A where screen G9 is displayed (S13: YES), the CPU 7 of terminal device 3A sorts the checkpoint histories 97 and 99 sent by user A from the checkpoint histories 97 to 99 displayed in the display area 74 and updates the display area 74 as shown in screen G10 (S14). The display area 74 displays checkpoint histories 97 and 99 generated by user A sending a notification, and does not display checkpoint history 98 generated by user B sending a notification. The CPU 7 returns to processing S2.

[0050] If checkpoint history 97 is selected from the display area 74 of terminal device 3A (S6:YES, S20:NO), the CPU 7 of terminal device 3A identifies user A as the sender of the notification based on the history ID "R7" (S23:YES, S24, S25). The CPU 7 of terminal device 3A determines that there are no notifications sent by user A before history information R7 (S26, S27:NO). The CPU 7 of terminal device 3A obtains R1 to R6 as history ID 41 for history information that was stored before history information R7 and whose user information 42 is user A, from among the multiple history information stored in the history information storage area 39. The CPU 7 of terminal device 3A identifies objects J1, J3, and J5, which correspond to the extracted history IDs R1 to R6, as target objects from among the objects J1, J3, J5, J8, J9, J11 to J16, J20, J21, and J24 displayed on the display unit 35 (S30). Since the target objects are identified from among the objects displayed on the display unit 35, objects that are deleted during the editing process and are not displayed on the display unit 35 are not included as target objects, even if they were edited during the target period. As shown in screen G11, the CPU 7 of terminal device 3A highlights the target objects J1, J3, and J5 for a predetermined time (S31, S32), and after the predetermined time has elapsed, it removes the highlighting of the target objects J1, J3, and J5 (S33). When terminal device 3 receives an instruction to terminate the main process, it sends a notification to server 2 to terminate the process and terminates the main process.

[0051] Referring to Figures 8 and 9, the notification sending process and notification display process performed in the main process of the first modified example will be described. In the main process of the above embodiment, when a notification is acquired and checkpoint history is selected, the history ID of the target period used to identify the target object is extracted. However, in the main process of the first modified example, a condition including the history ID generated in S3 is acquired as a condition for specifying the target period, and the history ID of the target period is extracted when sending the notification and stored in the flash memory 34.

[0052] The notification sending process in the first modified example shown in Figure 8 is the process executed in S4 of the main process in Figure 2. As shown in Figure 8, in the notification sending process, the CPU 7 searches for notifications stored before the history ID generated in S3 (S41), similar to S26. If there are notifications stored before the history ID generated in S3 (S42: YES), similar to S28, the CPU 7 extracts history information within the target period, using the period between the first checkpoint included in the conditions and the second checkpoint identified according to the first checkpoint as the target period (S43). If there are no notifications stored before the history ID generated in S3 (S42: NO), the CPU 7 extracts history IDs that are earlier than the history ID generated in S3 and whose user information matches (S44).

[0053] CPU 7 stores the history IDs extracted in S43 and S44 as history data in flash memory 34, associating them with the history IDs generated in S3 (S45). CPU 7 sends the history IDs generated in S3 and the history data stored in S45 along with the notification (S46). CPU 7 then finishes the notification sending process of this modified example and returns processing to the main process.

[0054] The notification display process of the first modified example shown in Figure 9 is the process executed in S7 of the main process in Figure 9. In Figure 9, the same step numbers are assigned to processes that are the same as the notification display process in Figure 5. As shown in Figure 9, the notification display process of the modified example differs from the others in that it performs processes S51 and S52 instead of processes S23 to S30. The process that is the same as in the above embodiment will not be explained, and the process of S51 that is different from the above embodiment will be explained below.

[0055] In S51, the CPU 7 obtains history data associated with the history ID of a notification or instruction to select a notification from another terminal device 3, which was obtained in the processing of S6 (S51). The CPU 7 identifies the object whose history data contains the history ID from among the objects displayed on the display unit 35 as the target object (S52).

[0056] Referring to Figure 10, the notification display process performed in S4 of the main process of the second modified example will be explained. In Figure 10, the same step numbers are assigned to processes that are the same as the notification display process in Figure 5. As shown in Figure 10, the notification display process of the second modified example differs from the notification display process of the above embodiment in that the process of S55 is performed instead of the process of S21. In reason In the first embodiment, the terminal device 3 that sends the notification assigns a history ID to the notification (S3) and sends the notification along with the assigned history ID (S4). However, in the second modified embodiment, the CPU 7 sends a notification without a history ID (S4) and stores the history information corresponding to the notification in the history information storage area 39 (S5). When a terminal device 3 receives a notification from another terminal device 3, it assigns a history ID to the received notification and stores the history information corresponding to the received notification, including the assigned history ID, in the history information storage area 39 (S55). In the second modified embodiment as well, the terminal device 3 can perform the same processing as in the above embodiment.

[0057] In the above embodiment, the terminal device 3, display unit 35, input unit 36, and communication unit 37 are examples of the computer, display unit, input unit, and communication unit of the present invention, respectively. The process in S10 is an example of the history storage step of the present invention. The process in S9 is an example of the display control step of the present invention. The process in S6 is an example of the condition acquisition step of the present invention. The process in S30 is an example of the identification step of the present invention. The processes in S31 to S33 are an example of the highlighting step of the present invention. The process in S5 is an example of the point storage step of the present invention. The process in S4 is an example of the notification step of the present invention. The process in S12 is an example of the list display step of the present invention. The process in S14 is an example of the extraction display step of the present invention.

[0058] In accordance with the display program of the above embodiment, the CPU 7 of the terminal device 3, which includes a display unit 35 and a CPU 7, performs the following processing. When the CPU 7 receives an editing instruction to edit an object (S8:YES), it stores history information that associates the object, the content of the editing of the object, and order information representing the editing order (S10). When the CPU 7 receives an editing instruction (S8:YES), it updates the object to be displayed on the display unit 35 (S9). The CPU 7 obtains a condition to specify a target period from the total period over which multiple history information is stored (S6). The CPU 7 identifies the object corresponding to the history information within the target period specified by the condition among the multiple history information as the target object from among the one or more objects displayed on the display unit 35 (S30). The CPU 7 highlights the identified target object (S31). By highlighting the target object on the display unit 35, the terminal device 3 executing the display program helps the user to easily distinguish between the target object edited during the target period and other objects among the one or more objects displayed on the display unit 35. Therefore, the highlighting step (S31) of the display program contributes to improving user convenience compared to conventional methods when checking the process by which the object displayed on the display unit 35 was edited to become the current object.

[0059] According to the display program of the embodiment, the CPU 7 of the terminal device 3 stores checkpoints that include sequence information and are used to identify the target period (S5). The CPU 7 acquires conditions that include information specifying the checkpoints (S6). The CPU 7 identifies the object corresponding to the history information within the target period separated by the checkpoints specified by the conditions among the multiple history information as the target object (S30). The terminal device 3 executing the display program highlights the target object on the display device 35, thereby making it easier for the user to distinguish between the target object edited during the target period separated by the checkpoints and other objects among the one or more objects displayed on the display device 35.

[0060] According to the display program of the embodiment, the CPU 7 of the terminal device 3 stores checkpoints that include sequence information and are used to identify the target period (S5). The CPU 7 acquires conditions that include information specifying the checkpoints (S6). The CPU 7 identifies the period between the first checkpoint specified by the conditions and the second checkpoint identified according to the first checkpoint as the target period, and identifies the object corresponding to the history information of the target period from among one or more objects displayed on the display unit 35 as the target object (S30). The terminal device 3 executing the display program highlights the target object on the display unit 35, thereby making it easier for the user to distinguish between the target object edited during the period between the first and second checkpoints and other objects among the one or more objects displayed on the display unit 35.

[0061] In S10, the CPU 7 stores the object, its edited content, sequence information, and user information to identify the user as history information. The CPU 7 stores checkpoints that include user information in addition to sequence information. In S5, the CPU 7 identifies the object that corresponds to the history information containing the user information of the checkpoint, within the target period defined by the checkpoint specified by the conditions among the multiple history information, as the target object. In S30, the terminal device 3, which executes the display program, highlights the target object on the display unit 35, thereby making it easier for the user to distinguish between the target object edited by the user of the checkpoint and other objects within the target period defined by the checkpoint, among the one or more objects displayed on the display unit 35. The display program contributes to improving user convenience when multiple users edit an object, allowing the user to check the edited content of a specific user.

[0062] CPU7 sends a notification to another user via the communication unit 37 of terminal device 3 (S4). teeth The system stores checkpoints in response to notifications being sent (S5). The terminal device 3, which runs the display program, can automatically store checkpoints when it sends notifications to other users. The display program can save the user the trouble of assigning checkpoints during the process of editing objects. The display program helps identify objects as target objects for the period corresponding to the sending of notifications to other users within the editing system 1.

[0063] In the modified version, CPU 7 stores a checkpoint containing the user information of another user upon receiving a notification from that user (S55). The display program can automatically store a checkpoint on the receiving terminal device even if the notification does not contain a checkpoint during the object editing process, saving the user the trouble of assigning checkpoints. The display program helps the user identify objects for a period corresponding to notifications sent by other users as target objects.

[0064] The CPU 7 transmits a notification and a checkpoint stored in response to the notification to another user via the communication unit 37 (S4). The display program can include a history ID in the notification, which helps ensure that the history ID received by the destination terminal device 3 is the same as the history ID stored in the history information storage area 39 of the sending terminal device 3. The display program also helps to omit the process of assigning a checkpoint on the receiving terminal device 3.

[0065] The CPU 7 displays one or more checkpoints in a list on the display unit 35 (S12). The CPU 7 extracts the checkpoint containing the specified user information from the one or more checkpoints and displays it on the display unit 35 (S13: YES, S14). The CPU 7 obtains the conditions that include the checkpoint specified by the input unit 36 ​​of the terminal device 3 from among the checkpoints displayed on the display unit 35 (S6). The terminal device 3, which executes the display program, contributes to obtaining the conditions that include the checkpoint specified by the user via the input unit 36. The user can easily select the checkpoint to be used to specify the period to be highlighted from among the list of checkpoints or the extracted checkpoints.

[0066] In response to the acquisition of the conditions in S6, the CPU 7 selects the period between the first checkpoint included in the conditions and the second checkpoint identified according to the first checkpoint as the target period and extracts historical information within that period (S28). The CPU 7 identifies the object corresponding to the extracted historical information from among the one or more objects displayed on the display unit 35 as the target object (S30). The terminal device 3 executing the display program can identify the target object by extracting historical information within the target period specified by the conditions in response to the acquisition of the conditions. Compared to the display program of the first modified example, which stores historical data extracted from the historical information within the target period, the display program of the above embodiment reduces the processing load when sending notifications and contributes to avoiding putting pressure on the storage area of ​​the flash memory 34 by storing historical data.

[0067] In the first modified example, the CPU 7 selects the period between the first checkpoint and the second checkpoint identified in accordance with the first checkpoint as the target period, and obtains a condition that includes historical data extracted from the historical information within the target period (S51). In the first modified example, the CPU 7 identifies the object corresponding to the historical data from among the one or more objects displayed on the display unit 35 as the target object (S52). The display program contributes to simplifying the process of identifying the target object compared to the case where the condition does not include historical data.

[0068] The CPU 7 highlights the target object on the display unit 35 for a predetermined time from among one or more objects displayed on the display unit 35 (S31 to S33). The terminal device 3, which executes the display program, contributes to saving the user the trouble of inputting an operation to return the highlighting to the normal display. The terminal device 3 contributes to improving user convenience when highlighting the target object.

[0069] Honpatsu AkiraThe display program and display method are not limited to the embodiments described above, and various modifications may be made without departing from the spirit of the present invention. For example, the following modifications may be made as appropriate. The present invention can be implemented in various forms, and may be realized, for example, in the form of a non-temporary computer-readable medium storing a display program, a display device, and a display system.

[0070] In the above embodiment, the terminal device 3 is not limited to a tablet terminal, but may be a smartphone, personal computer, dedicated terminal, etc. The display unit 35 of the terminal device 3 only needs to be capable of displaying images, and may be, for example, an organic EL display, plasma display, plasma tube array display, or electronic paper display using electrophoresis, etc. The input unit 36 ​​of the terminal device 3 may be a touch panel, keyboard, mouse, joystick, etc. The terminal device 3 may be shared by multiple users. The main processing may be performed on the editing system 1, which consists of a server 2 and a single terminal device 3, or it may be performed on a terminal device 3 that does not communicate with the server 2. The communication unit 37 may be omitted.

[0071] Object attributes may include types other than strokes, markers, text, shapes, and images, or they may include some types of strokes, markers, text, shapes, and images, such as only text.

[0072] The timing of storing history information may be changed as appropriate; for example, it may be stored in the history information storage area 39 after each editing operation. The history information may be information that associates an object, the content of the object's editing, and sequence information representing the editing order, and may or may not include user information, or it may include other information. The sequence information may include the editing date and time, as well as information that can identify the storage order of the history information, such as a history ID.

[0073] The method for generating and storing checkpoints may be modified as appropriate. For example, the CPU 7 may display a checkpoint generation button on the display unit 35 and generate a checkpoint when the generation button is pressed. The CPU 7 may automatically generate a checkpoint when a predetermined button displayed on the display unit 35, such as an overwrite save button, is selected. The CPU 7 may automatically generate checkpoints according to predetermined timings (for example, every 10 minutes, at a specific time, etc.). The terminal device 3 may acquire checkpoints generated by the server 2. Checkpoints may be generated by the CPU 6 of the server 2 and transmitted to each terminal device 3. Checkpoints may be stored separately from history information.

[0074] The display program, which includes instructions for executing the main process, only needs to be stored in the memory device of terminal device 3 before the CPU 7 of terminal device 3 executes the display program. Therefore, the method of acquiring the display program, the acquisition path, and the device that stores the program may be changed as appropriate. The display program executed by terminal device 3 may be received from other devices via cable or wireless communication and stored in a memory device such as a memory unit. Other devices include, for example, PCs and servers connected via a network.

[0075] Each step of the main process is not limited to being performed by CPU7, but may be partially or entirely performed by other electronic devices (e.g., ASICs). Similarly, each step of the main process is not limited to being performed by CPU7, but may be partially or entirely performed by other electronic devices. Each step of the main process may be distributed among multiple electronic devices (e.g., multiple CPUs). Each step of the main process can be reordered, omitted, or added as needed. The following modifications may be made to the main process as appropriate.

[0076] CPU7 may omit S32 and S33 and terminate the highlighting of the target object started in S31 if it detects an instruction to remove the highlighting. CPU7 may omit S11 and S12 and not display the list of checkpoints. CPU7 may omit S13 and S14 and not display the checkpoints sorted by specific conditions. The specific conditions used to sort the checkpoints may be changed as appropriate depending on the method of generating the checkpoints.

[0077] The conditions for specifying the target period and the method for identifying the target conditions may be changed as appropriate. CPU7 may omit the processing from S25 to S28 and set the period prior to the checkpoint of the history ID obtained in S23 as the target period, regardless of whether a checkpoint prior to the history ID obtained in S23 is stored. CPU7 may set the period between two selected history information items from the list of history information displayed in the display area 74 as the target period. In this case, the history information may be information generated in response to editing operations, or information generated in response to specific operations such as button selection. CPU7 may set the period before or after one selected history information item from the list of history information displayed in the display area 74 as the target period. In these cases, the target period may be the period that includes the selected history information, or it may be the period that does not include the selected history information. CPU7 may identify the target period by excluding the period specified by the conditions from the total period in which multiple history information items are stored. CPU7 may obtain a condition that includes a specific time and set the period delimited by the obtained time as the target period.

[0078] The method for identifying the target object may be changed as appropriate. The CPU 7 may omit the processing in S25 and perform the same processing by searching for notifications sent by any user in S26. In this case, the target object identified in S30 is all objects among the objects displayed on the display unit 35 that correspond to the history information within the target period specified by the conditions. The CPU 7 may identify multiple users specified by the conditions in the processing in S25 and search for notifications sent by the identified multiple users in S26. In this case, the target object identified in S30 is objects among the objects displayed on the display unit 35 that correspond to the history information corresponding to the editing operations of the identified multiple users within the target period specified by the conditions. The CPU 7 may omit S2 to S5 and be unable to send notifications to other terminal devices 3. Each of the above embodiments and the above modifications may be combined with each other to the extent that they do not cause contradictions. The applicant intends to obtain patent rights not only for the combinations exemplified in the claims but also for embodiments that combine each other to the extent that they do not depart from the gist of the present invention and do not cause contradictions. [Explanation of Symbols]

[0079] 1: Editing system, 3, 3A, 3B, 3C: Terminal devices, 6、 7: CPU, 32: ROM, 33: RAM, 34: Flash memory, 35: Display unit, 36: Input unit, 37: Communication unit

Claims

1. A computer comprising a display unit and a control unit, the control unit of which, A history storage step involves storing history information that associates the object, the content of the edits on the object, and sequence information representing the editing order, in response to receiving an edit instruction to edit an object. A display control step to update the object displayed on the display unit in response to receiving the editing instruction, A notification step of sending a notification to another user via the communication unit provided by the computer, A point storage step in which checkpoints, including the sequence information, are stored in response to the transmission of the notification, which are used to identify a target period within the entire period in which the multiple historical information is stored. A condition acquisition step to acquire a condition that specifies the target period, which includes information specifying the checkpoints, A selection step of identifying, among one or more objects displayed on the display unit, the object corresponding to the history information within the target period separated by the checkpoint specified by the conditions among the plurality of history information, as the target object; A highlighting step in which the identified target object is highlighted A display program characterized by including instructions for executing a command.

2. The condition acquisition step acquires the condition including information specifying the checkpoint, The display program according to claim 1, characterized in that the specified step involves specifying the period between a first checkpoint specified by the conditions and a second checkpoint specified according to the first checkpoint as the target period, and specifying the object corresponding to the history information for the target period among the one or more objects displayed on the display unit as the target object.

3. The history storage step stores the object, the edited content, the sequence information, and user information that identifies the user, as history information, in association with each other. The point storage step stores the checkpoints, which include the user information in addition to the sequence information. The display program according to claim 1 or 2, characterized in that the identifying step identifies, among the one or more objects displayed on the display unit, the object that falls within the target period delimited by the checkpoints specified by the conditions among the plurality of history information, and that corresponds to the history information containing the user information of the checkpoint, as the target object.

4. The display program according to claim 3, characterized in that the point storage step stores the checkpoint including the user information of the other user in response to receiving a notification from the other user.

5. The display program according to claim 1 or 2, characterized in that the notification step transmits the notification and the checkpoint stored in response to the notification to the other user via the communication unit.

6. The display unit includes a list display step that displays one or more of the checkpoints in a list, Extraction and display step: Extracting the checkpoint containing the specified user information from the one or more checkpoints and displaying it on the display unit. Includes instructions for further implementation, The display program according to claim 3, characterized in that the condition acquisition step acquires the condition, which includes the checkpoint specified by the computer's input unit, from among the checkpoints displayed on the display unit.

7. The display program according to claim 2, characterized in that the specified step, in response to the acquisition of the condition, extracts the history information within the target period, with the period between the first checkpoint included in the condition and the second checkpoint identified according to the first checkpoint being selected as the target period, and identifies the object corresponding to the extracted history information among the one or more objects displayed on the display unit as the target object.

8. The condition acquisition step involves selecting the period between the first checkpoint and the second checkpoint identified according to the first checkpoint as the target period, and acquiring the condition including historical data extracted from the historical information within the target period. The display program according to claim 2, characterized in that the specified step identifies the object corresponding to the history data among the one or more objects displayed on the display unit as the target object.

9. The display program according to claim 1 or 2, characterized in that the highlighting step highlights the target object among the one or more objects displayed on the display unit for a predetermined time.

10. A display method performed by the control unit of a computer comprising a display unit and a control unit, A history storage step involves storing history information that associates the object, the content of the edits on the object, and sequence information representing the editing order, in response to receiving an edit instruction to edit an object. A display control step to update the object displayed on the display unit in response to receiving the editing instruction, A notification step of sending a notification to another user via the communication unit provided by the computer, A point storage step in which checkpoints, including the sequence information, are stored in response to the transmission of the notification, which are used to identify a target period within the entire period in which the multiple historical information is stored. A condition acquisition step to acquire a condition that specifies the target period, which includes information specifying the checkpoints, A selection step of identifying, among one or more objects displayed on the display unit, the object corresponding to the history information within the target period separated by the checkpoint specified by the conditions among the plurality of history information, as the target object; A highlighting step in which the identified target object is highlighted A display method that includes the following features.

Images