JPH11110200A - Designing device and designing method for user interface - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make an action designing performable via a simple link setting when the transmission of a message to a certain object is desired right after the message of another object is called. SOLUTION: When a user designates an object and selects 'manual event setting', an event name list 702 is displayed for the event of the object designated by the user. Then, an event setting dialog 706 is displayed when a production button 703 is clicked. When a button 707a is clicked in a message selection area 707, a message name list is displayed for the message that is received by the designated object. The user selects the user's desired message name out of the message name list and clicks an OK button 709 after setting the input of the event name in an event name input area 708. Thus, the event of the name designated by the user against the message name designated by the user is produced and set to the designated object and this event name is added to the list 702.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a screen design and operation design for a system that receives an input from a user operation and uses an operation screen in which parts are laid out as a user interface (UI). The present invention relates to a user interface design apparatus and a method suitable for performing the method using the above method.

[0002]

2. Description of the Related Art There are many tools for designing an operation screen and an operation by GUI operation.

For example, if Visual Basic (registered trademark of Microsoft Corporation in the United States) is used, programming of Windows (registered trademark of Microsoft Corporation in the United States) can be easily performed by using a GUI operation.

AUTHORWARE STAR (Macromedia, USA)
(Registered trademark) enables a system such as presentation and information guidance to be easily constructed by an authoring operation such as arranging icons.

[0005]

However, while a visual programming tool such as VisualBasic can construct a user interface for performing a complicated operation, most of the operation design is performed by writing a program code. You need to learn.

On the other hand, an authoring tool such as AUTHORWARE STAR can describe operations such as screen transition by GUI operation, but complicated operations such as different screen transition destinations depending on an internal state when a certain button is pressed. It is difficult to describe.

[0007] The inventors of the present invention have disclosed in Japanese Patent Application No. 8-3148.
No. 47 proposed a user interface design apparatus and method that can easily design an operation process by linking between objects and can easily perform complicated processes such as conditional branching.

However, in this design apparatus and method, when a certain object takes action when a message is received and a message is sent to another object due to the action, many links are set. There is a problem that must be.

SUMMARY OF THE INVENTION The present invention has been made to solve the above-mentioned problem, and an object of the present invention is to simplify a complicated event or message when setting a link between objects using a user interface designing apparatus. To be able to set it.

Another object of the present invention is to realize a design of this operation with a simpler link setting when it is desired to transmit a message to another object immediately after a message of one object is called. It is to make.

Still another object of the present invention is to enable a necessary event to be automatically created and added when it is desired to send a message to another object immediately after a message of one object is called. It is in.

[0012]

A configuration according to a first aspect of the present invention is to arrange various component objects such as text and images at arbitrary positions on a screen object representing an operation screen of a user interface, and In a user interface design apparatus for designing an operation by linking from a part object to another object, a link setting receiving means for receiving designation by a user operation of a link source object and a link destination object to be linked And event list display means for displaying a list of event names of the events that can be received by the link source object received by the link setting receiving means; and a message of a message by which the link destination object received by the link setting receiving means is received First name Message list display means for displaying a list, event selection means for accepting selection of an event name by a user operation from the list of event names, and accepting selection designation of a message name by a user operation from the list of message names A link for setting a link having an attribute including a message to the link source object having the event name received by the message selecting means and the event name received by the event selecting means, and a message to the link destination object having the message name received by the message selecting means. And setting means.

In such a configuration, when a user (designer) specifies a desired link source object and a link destination object at the time of setting a link between objects, the event name of an event that can receive the specified link source object List, the list of message names of messages that can receive the specified linked object is automatically displayed, and the user simply selects and specifies the desired event name and message name from the list, and the user selects and specifies the event Since a link having an attribute including an event of a link source object having a name and a message to a link destination object having a message name selected and designated by a user is automatically set, complicated events and messages can be easily set.

According to a second aspect of the present invention, there is provided a message selecting means for receiving a user's operation of selecting a message from a list of message names of messages for which a user-specified object can be received, and the message selecting means. Event name input means for receiving an input by a user operation of an event name of an event to be newly generated separately from an event set in advance in a user-specified object, indicating that a message having a given message name has been called, An event creating means having an event name accepted by the event name input means and newly creating an event indicating that the message of the message name accepted by the message selecting means has been called; and User-specified object Characterized by comprising an event additional means for adding configure the list of events.

In such a configuration, the user selects and specifies a message name of a message that can receive the object specified by the user from a list, and specifies an event name of a new event indicating that the message is called. By simply inputting, it is possible to create an event having an event name specified and input by the user and indicating that a message having a message name selected and specified by the user has been called. Therefore, when it is desired to transmit a message to another object immediately after a message of a certain object is called, the design of this operation can be realized with a simpler link setting.

Here, in the configuration according to the second aspect, an event list display means for displaying a list of event names of events that can receive a user-specified object, and a user operation from the displayed list of event names An event selecting means for accepting the selection designation of the event name of the event to be deleted and an event deleting means for deleting the event of the event name accepted by the event selecting means from the above event list are added. If an event with an event name selected and designated can be deleted, more flexible operation design is possible.

In the configuration according to the third aspect of the present invention, when a link destination object and a message passed to the object are specified by a user operation for linking, the user-specified message is called. An event presence / absence determining means for determining whether or not an event indicating that the event has already existed, and an event indicating that the user-specified message has been called in accordance with the determination result of the event presence / absence determining means. Automatic event creating means for adding to the user-specified object.

In such a configuration, when the user specifies a link destination object and a message to be passed to the object for link setting, if there is no event indicating that the user-specified message has been called, For example, a new event indicating that the user-specified message has been called is automatically created and added to the user-specified object. In this way, when a message of an object is called and a message is to be sent to another object immediately, the operation can be designed with a simpler link setting,
The required events will be added automatically.

Here, in the configuration according to the third aspect, the link deletion means for deleting the link designated by the user, the link deleted by the link deletion means, the link destination object, and the message passed to the object are the same. Link presence / absence determination means for determining whether or not a link exists, and according to the determination result of the link presence / absence determination means,
It is preferable to add an automatic event deletion unit for deleting an event indicating that the message passed to the link destination object is called.

In such a configuration, when the user performs an operation of deleting a link, it is confirmed by the link presence / absence determining means that the message used for that link is not used for another link. If so, the event corresponding to the message is deleted. That is, a newly added event is automatically deleted when it is no longer needed.

Further, in the configuration according to the third aspect, an event deleting means for deleting an event designated by the user, a link searching means for searching for a link using the event deleted by the event deleting means, and the link It is preferable to add an automatic link deletion unit for deleting the link searched by the search unit.

In such a configuration, when the user performs an operation of deleting an event, if it is confirmed by the link searching means that no link using the event exists, the event is used. The link you were using is automatically deleted. That is, when a newly added event is deleted, a link using the event is automatically deleted, as it is indispensable.

[0023]

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

(1) Configuration of User Interface Design Apparatus First, the configuration of the user interface design apparatus will be described.

FIG. 1 is a block diagram showing a configuration of a user interface design apparatus according to one embodiment of the present invention.

As shown in FIG. 1A, a user interface (UI) design device according to the present embodiment
U, a main memory, and a computer main body 10 incorporating a large-capacity storage device such as a floppy disk device, a hard disk device, or a CD-ROM device (none is shown)
Input means such as a keyboard 11, a mouse 12, a microphone 13 (for voice input), a touch panel 14 (for touch input), a display (display device) 15, a speaker 16 used for outputting voice and sound, and the like. (Known as a computer). Here, the touch panel 14 is formed integrally with the display screen of the display 15.

FIG. 1B shows a user interface (U)
I) The functional configuration of the design device is shown. That is, the user interface (UI) design device in the present embodiment is the same as that shown in FIG.
An output device 101 realized using output means such as a display 15 and a speaker 16 in FIG. 1A and an input device such as a keyboard 11 and a mouse 12 shown in FIG. An input device (hereinafter, referred to as a design-time data input device) 102 used for inputting data and the like, and a user interface design mechanism (hereinafter, a UI design mechanism) for interactively interacting with a designer or a user at the time of design and simulation. 1) and an input device (hereinafter referred to as a simulation input) which is realized using input means such as a keyboard 11, a mouse 12, a microphone 13, and a touch panel 14 in FIG. 1)
04 and a database (DB) 105 (for example, realized using a hard disk device) 105 for storing and managing designed screen information, operation information, and data materials.
And a memory 106 (realized using a main memory) that provides an area for temporarily storing designed screen information, operation information, data materials, and the like, a work area, and the like.

The UI design mechanism 103 includes an editing unit 107 for managing screens and operations at the time of design, and a UI
And a prototype execution unit 108 which manages the simulation at the time of confirming the operation of I. The configurations of the editing unit 107 and the prototype execution unit 108 will be described later.

The UI design mechanism 103 is the center of the UI design apparatus, and its functions are the same as those shown in FIG.
(A) a storage medium storing a program to be executed by the computer main unit 10 therein, for example, a CD-ROM
17, the CD-ROM 17 is mounted on the computer main body 10 (the CD-ROM device therein), and the CD-ROM 17 is mounted.
This is realized by causing the computer main body 10 to read and execute a program recorded in the ROM 17.
The program read by the computer main body 10 may be transferred via a communication medium.

(2) Outline of UI Design Mechanism 103 Next, an outline of the UI design mechanism 103 will be described with reference to a screen image example of FIG.

The UI design mechanism 103 has a UI screen specification,
This is a tool for designing operation specifications using a GUI. The screen design by the UI design mechanism 103 is performed on a card layout manager window (CLMW) 201. That is,
Screen object (object in object orientation) representing the UI operation screen on CLMW201
A card 202 is created as a text component 203, an image component 204, and the like (UI) on the card 202.
The screen is designed by laying out the component objects (which constitute the operation screen).

At the time of design by the UI design mechanism 103, a map viewer 205 is displayed together with the CLMW 201. The map viewer 205 is a window for listing and displaying created cards. On the map viewer 205, card icons that are reduced images of the created cards are displayed. In the example of FIG. 2, a plurality of card icons including the card icon 206 are displayed. When the number of cards already created is large, only card icons corresponding to some cards are displayed on the map viewer 205, and card icons corresponding to the remaining cards are scrolled up and down or left and right on the map viewer 205. Will be displayed. Also,
If a component (component object) arranged on the card has a link to another card, a link and an arrow (link line) indicating the direction are displayed between the corresponding card icons.

(3) Types of Manager Next, the types of managers (management means) included in the editing unit 107 and the prototype execution unit 108 in FIG. 1 will be described.

First, the editing unit 107 shown in FIG.
Are a card layout manager (CLM) 109 for generating and managing the card 202, and a part (part) manager (P) for generating a component object on the card 202.
M) 110.

When the CLM 109 is activated, the card 20
2 and editing of component objects laid out on the card 202, and link setting for operation processing performed in response to an event from the user (such as clicking a button or performing voice input).

The PM 110 is activated by the CLM 109, generates a component object specified by the user, and registers the generated component object in the card 202. The management of the component objects registered in the card 202 is performed by the card (screen object) 202.

On the other hand, the prototype execution unit 108 in FIG.
Is composed of a prototype manager (PTM) 111. The PTM 111 sets C according to an instruction from the user.
It is started by the LM 109. When the PTM 111 is started, the component object that has received the event from the user sends a message to the set link destination by using the message transmission function. By repeating this message transmission, an operation simulation can be performed as designed for the link.

(4) Description of Design Operation Next, the design operation of the UI design apparatus (the UI design mechanism 103 in FIG. 1) will be described. This design operation is executed by the editing unit 107 in the UI design mechanism 103 in accordance with an instruction from the designer. The state during the design is called a design mode. On the UI design apparatus according to the present embodiment, it is necessary to perform two operations of designing a screen image in which components are arranged and designing an operation scenario as described below.

(4-1) Design of Screen Image (4-1-1) Activation of CLM When the designer starts up the UI design mechanism 103 in FIG.
The CLM 109 in the editing unit 107 of the UI design mechanism 103 is activated. When the CLM 109 is activated, the information (designed screen information, operation information, data materials, and the like) stored in the DB 105 is read into the memory 106, and as shown in FIG. A CLMM) 207 and a card layout manager window (CLMW) 201 are displayed on the display of the output device 101 on a screen. CLM
M207 has items of “card”, “card display”, “edit”, “information setting”, “link”, and “prototype execution”.

In the screen display state of FIG. 2, the designer operates the design-time data input device 102 (for example, a mouse) to
When the cursor is moved to the item of “card” in the MM (card layout manager menu) 207 and the mouse is clicked to select “card”, the “card” is selected.
Are displayed by the CLM 109. In the “card” submenu, for example, “new card”, “call out card parts”, and “end” are prepared. Then, when the designer moves the cursor to “new card” and selects it, a new card is generated by the CLM 109 and displayed on the CLMW 201. The generated card information (screen object) is stored in the memory 1
06.

In order to design a screen (UI operation screen), a desired card 202 may be displayed, and a desired component object may be arranged there.

Here, in order to display a desired card,
First, the designer moves the cursor to the “card display” item in the CLMM 207 and clicks on the item, and the “card display”
Display the submenu corresponding to. In this submenu, for example, items “next card” and “previous card” are prepared. Meanwhile, the created card (information of)
Are stored and managed in the creation order (here, logical order) in the DB 105, and are read into the memory 106 at this stage as described above.

Therefore, when the designer selects the "next card", the card created one card after the currently displayed card is
When the “previous card” is selected, the card created immediately before the currently displayed card is stored in the memory 106 by the CLM 109.
And is displayed on the CLMW 201. The card 202 displayed on the CLMW 201 in FIG.
Is a card read from the memory 106 in this manner or a newly created card. Note that FIG.
FIG. 2 shows a state where various card components (component objects) are arranged on the card 202, but it is assumed that the card 202 has not been arranged at this stage.

To generate a component object to be arranged on the card 202 displayed as described above, the designer first selects the "card component call" submenu of "card" of the CLMM 207.

(4-1-2) Startup of PM When “call card parts” is selected, the CLM 109
Starts the PM 110. When the PM 110 is started, a parts manager menu (PMM) 208 shown in FIG. PMM2
08 includes items such as “text button creation”, “text component creation”, “image creation”, and “end”.

(4-1-3) Creation of Text Button The text button is a button-shaped part (part object) that can display a character string specified by the designer (has a procedure).

In order to generate a text button, for example, the text button 300 shown in FIG. 3 and place it on the card 302 (corresponding to the card 202 in FIG. 2), first, the designer sets the design time data input device 102 (medium). The mouse is operated to move the cursor to "Create Text Button" of the PMM (Parts Manager Menu) 208 in FIG.
In response, PM 110 displays a text button information setting dialog 301 as shown in FIG. The designer sets the attributes of the text button 300 on the text button information setting dialog 301.

As is apparent from FIG. 3, the attributes to be set for creating the text button 300 include the component name, the horizontal size of the component, the vertical size of the component, the X position on the card (here, the card 302). X coordinate), Y position (Y coordinate),
There are a background color of a part, a character color, a character font (type), a text content, a state where a prototype is being executed (simulation is being executed), and the like. The status of running prototype is
For example, when the card 302 is displayed (the card 3
The initial state of the text button 300 (located in the area 02). The state of the text button 300 includes “display state” or “non-display state”.

The designer inputs these attribute values on the text button information setting dialog 301 by operating the design time data input device 102 (the mouse or keyboard therein).
An OK button 303 provided in the information setting dialog 301 is clicked. Then, the PM 110 creates a text button 300 in which the input attribute value is set,
(Corresponding to the card 202 in FIG. 2) is displayed on the displayed card 302 shown in FIG.
(Information of the card component) is stored in the memory 106 as the (part information) of the component object of the card 302.

If it is desired to cancel the creation of the text button, the designer may click the Cancel button 304 provided in the text button information setting dialog 301. In this case, PM110
The text button information setting dialog 301 is hidden, and the text button creation processing is stopped.

The horizontal size of the component, the vertical size of the component,
Attribute values such as the X position and the Y position on the card can also be set by a position designation operation on the card 302 using a mouse.

(4-1-4) Creation of Text Component The text component is a board-shaped component (having a procedure) that can display a character string specified by the designer.

In order to generate a text component, for example, the text component 203 shown in FIG. 2 (and place it on the card 202 as shown in FIG. 2), the designer first inputs
02 (mouse in the middle) to move the cursor to “Create text part” of the PMM 208 in FIG. 2 to select it. The following is the same as the case of generating the text button 300 described above.

(4-1-5) Creation of Image Parts Image parts are parts (having procedures) that can display data (image data) of an image file specified by a designer, and are normally pressed and pressed. This is a component (with procedures) that can specify (for example, a file name) an image file at the time.

In order to generate an image component, for example, the image component 204 shown in FIG. 2 (and place it on the card 202 as shown in FIG. 2), the designer first inputs the design-time data input device 1.
02 (the middle mouse) is operated to move the cursor to "Create Image" of the PMM 208 in FIG. The following is the same as the case of generating the text button 300 described above. The attributes to be set for creating the image component 204 include a component name, a horizontal size of the component, a vertical size of the component, an X position and a Y position on the card, a normal image file, an image file when pressed, and a prototype execution. There are states such as inside.

As described above, the screen image can be designed. The card (screen object) generated by the design of the screen image and various component objects (information of) arranged on the card are stored in the memory 1.
06 to the DB 105 and stored in the DB 105.

(4-2) Design of Operation Scenario When the designer finishes designing the screen image, he or she designs the operation scenario. The design of the operation scenario in the present embodiment is performed by setting a link between objects by, for example, operating a mouse. The link includes a link from the part object to the card (screen object),
There is a link from the part object to the part object.

The design of an operation scenario will now be described in the order of link and link setting procedure, link information list window, link deletion, event creation, etc., which are related to the design of the operation scenario.

(4-2-1) Link The link is passed to a link name (link identification tag) for identifying the link, a pointer to the link source object, a pointer to the link destination object, and a link destination object. This is an object (link object) having an attribute such as a message to be transmitted. There are two types of links (link objects): a link from a component object to a card (screen object) and a link from a component object to a component object.

(4-2-1-1) Link setting from the component object to the card Here, the link setting from the component object to the card (screen object) is performed by pressing the text button on the screen during the execution of the prototype. An example of a link setting operation for designing an operation of hiding (hiding) a part and a text part will be described with reference to the screen example of FIG. 4 and the flowchart of FIG.

Now, the display of the output device 101
As shown in FIG. 4, a card 4 constituting a target screen
00 (# 1) and a map viewer 408 (corresponding to the map viewer 205 in FIG. 2) are displayed. On the card 400, two text buttons 40
1, 412 and an image component 413 are arranged. The map viewer 408 includes a card 400 (#
The card icon 409 as the reduced image of 1), the card icon 410 of the card (card # 0) on which the link source component of the card 400 is arranged, and the card 400
A card icon 411 of a card (card # 2) for which a link is to be set from the upper part (here, the text button 401) is displayed. Although the CLMM 207 in FIG. 2 is also displayed on the display of the output device 101, it is omitted in FIG.

When setting a link in such a state,
First, the designer operates the design-time data input device 102 (the mouse therein) to click and select a component object to be a link source from the component objects arranged on the card 400. Here, the text button 40
It is assumed that 1 has been selected.

Next, the designer moves the cursor to the “link” item in the CLMM 207 (see FIG. 2) and clicks on it, and changes the submenu corresponding to the “link” to the CL menu.
It is displayed by M109. This submenu contains:
An item called “link setting” is provided. Then, when the designer selects “link setting”, the CLM 109 displays a link setting dialog 402 as shown in FIG. 4, and the part object (the text button 401 in this case) previously selected from the card 400 is linked to the link source. (Step S1,
S2).

The link setting dialog 402 displays a link name input area 403 for inputting a link name, and a list of events (event names representing) in which the link source object can be received. Selection area 40 that allows the user to select an event
4, a message selection area 405 that displays a list of messages (message names representing) to which the linked object can be received, and allows the designer to select a message from the list, an OK button 406, and a Can button.
A cel (cancel) button 407 is arranged.

When the link setting dialogue 402 is displayed, the designer clicks the card icon 411 on the map viewer 408 corresponding to the card to which the text button 501 is linked, thereby changing the transition destination (link destination).
Screen (card) is selected and designated (step S3). At this time, the clicked card icon 411 is highlighted so that the designer can easily recognize it (step S4). Here, selection marks 421 indicating that the card icon 411 has been selected are displayed at the four corners. The card icon 409 corresponding to the displayed card 400 (# 1), that is, the card 400 (# 1) on which the component object (the text button 401) selected as the link source is placed, is indicated by the designer. The card icon is displayed (highlighted) in a predetermined color different from other card icons so as to be easily visually recognized. The text button 401 selected as the link source is displayed (highlighted) in a predetermined color different from other components so that the designer can easily recognize the text button 401.

In this state, the designer sets the link name input area 4
A desired link name (for example, link 1) is input and set to 03 (steps S5 and S6). By clicking the list call button 404 a in the event selection area 404, the designer indicates the event of the text button 401 as a link source such as “pressed”, “released”, “clicked”, and the like. Event list 417 is displayed (pull-down display here), a desired event is selected from the list 417, and
04 (steps S7 to S9). In the example of FIG. 4, a state in which the event “pressed” is selected is shown. In addition, the designer selects the message selection area 405
By clicking the list call button 405a, a list (not shown) of messages (message names representing) such as “display” and “non-display” is displayed, and a desired message (here, “display”) is displayed from the list. ) Is selected and set in the area 405 (steps S10 to S1).
2). As described above, the designer performs input setting of a link name in the link name input area 403, selection of an event in the event selection area 404, and selection of a message in the message selection area 405.

When the above setting is completed, the designer clicks an OK button 406 (step S13). Then, CLM 109 is selected and specified as a link destination (corresponding to card icon 411) from text button 401 (on card 400) selected and specified as a link source.
Link (link object) 416 to the card (indicated by an arrow in the figure, but not displayed on the screen here)
Is created, and the link name (link name 1) and the link source object (card 400
A pointer pointing to the upper text button 401), a pointer pointing to the link destination object (the card corresponding to the card icon 411), an event of the link source object ("pressed"), a message to the link destination object ("display") Is set, the information of the link 416 is stored in the memory 106, and the link setting dialog 40 is set.
2 is not displayed (step S14).

(4-2-1-2) Link setting from component object to component object Next, regarding the link setting from the component object to the component object, when the text button on the screen is pressed during the execution of the prototype, the image component is set. An example of a link setting operation for designing an operation in which another text button is hidden will be described with reference to FIGS. 4 and 9 described above.

First, the designer operates the design-time data input device 10.
2 (the middle mouse) is operated to click and select a part object to be a link source from the part objects arranged on the card 400. Here, it is assumed that the text button 412 has been selected.

Next, as in the case of setting the link from the component object to the card, the designer sets the CLMM2
07 (refer to FIG. 2), move the cursor to the item of "Link" and click on it, and select "Link setting" from the submenu while the submenu corresponding to the "Link" is displayed by the CLM 109. I do. Then CL
The link setting dialog 402 is displayed by M109, and it is determined that the component object (here, the text button 412) selected from the card 400 is specified as the link source (step S).
1, S2).

Next, the designer selects (the text button 41) from among the component objects arranged on the card 400.
By clicking a component object to be a link destination (for example, image component 413), a component object at the link destination is selected and designated (step S3). At this time, the link source and the link destination components are displayed (highlighted) in a predetermined color different from other components so that the designer can easily visually recognize that (step S4).

In this state, the designer sets the link name input area 4
03 to input a desired link name (step S
5, S6), click the list call button 404a in the event selection area 404 and click the event list 417.
Is displayed, and, for example, “pressed” is selected as an event of the link source text button 412 from the list 417 (steps S7 to S9), and a list call button 405a of the message selection area 405 is clicked to display a message list. Is displayed, and a linked part object (here, image part 4
13) A "non-display" message for hiding the message is selected (steps S10 to S12).

When the designer clicks the OK button 406 (step S13), the CLM 109 uses the text button 412 on the card 400 selected and designated as a link source on the same card 400 selected and designated as a link destination. A link (link object) 414 (shown by an arrow in the figure but not displayed on the screen) to the image part 413 is created, and the link 41 is created.
4, a link name, a pointer to the link source object (text button 412), a pointer to the link destination object (image part 413), an event of the link source object ("pressed"), and a link to the link destination object. A message ("non-display") is set, the information of the link 414 is stored in the memory 106, and the link setting dialog 402 is hidden (step S14).

Subsequently, in the same procedure, the text button 41
By selecting and specifying 2 as a link source and selecting and specifying the text button 401 as a link destination, a link (link object) 415 from the text button 412 to the text button 401 on the same card 400 is created. , A pointer to the link source object (text button 412), a pointer to the link destination object (text button 401), an event of the link source object ("pressed"), a message to the link destination object ("Hide" message) and set its link 41
5 is stored in the memory 106.

(4-2-2) Link List Information Window As described above, in the UI design apparatus having the configuration shown in FIG. 1 (the inside UI design mechanism 103), a plurality of links are set from one object. It is possible. For this reason,
The link structure may be complicated. Therefore, in the present embodiment, a link information list window that lists link information on objects specified by the designer can be displayed so that the designer can easily grasp the complicated link structure on the screen. The screen configuration of the link information list window will be described with reference to the screen example of FIG. 5 and the flowcharts of FIGS.

First, the link information list window 501 in FIG. 5 has a link destination list page 502 and a link source list page 503.

The link destination list page 502 is a page displaying a list of links (link names representing) from which a certain object is a link source. On the other hand, the link source list page 503 is a page displaying a list of links (link names representing) to which an object is a link destination.

The link destination list page 502 has a link destination list tab 504, and the link source list page 503 has a link source list tab 505. Tab 50
4, 505 are always displayed on the link information list window 501. When the tab (link destination list tab) 504 is clicked, the entire link destination list page 502 is displayed. When the tab (link source list tab) 505 is clicked, the link is clicked. The entire source list page 503 is displayed. FIG. 5 shows a state where the link destination list page 502 is displayed.

The link destination list page 502 includes a list (link name list) 506 of link names of links set using the specified object as a link source, a “link delete” button 507 for deleting the set links, and There is. The link destination list page 502 further includes a link destination part type display area 508 and a link destination part name display area, which are four areas for displaying attribute information of the link having the link name selected from the link name list 506. 509, event display area 510, and message display area 511
And a "close" button 512.

On the other hand, on the link source list page 503, a list of link names of links set with the specified object as the link destination, a “link delete” button, a link source component type display area, a link source component name, Display area, event display area, message display area, and "close"
There are buttons (both not shown).

Next, a procedure for using the link information list window 501 will be described.

Now, as shown in FIG. 5, the card 522 and the map viewer 523 constituting the initial screen are connected to the output device 1.
01 (step S21). The card 522 includes a text button 520, two text buttons 524a and 524b that are link destinations of the text button 520, and a text button 5 that is a link source of the text button 520.
25, and a card icon 531 corresponding to the card 522 and a card icon 532 corresponding to the card 528 to which the component on the card 522 is linked are displayed in the map viewer 523. I do.

Here, in order to display a link information list window 501 relating to a certain object on the card 522, for example, the text button 520, the following operation is performed.

First, the designer operates the design-time data input device 10.
2 (the middle mouse) to click and select the text button 520 on the card 522 (step S2).
2). Next, the designer selects the item “link” of the CLMM 207.
Is moved and clicked to display a submenu corresponding to the "link". In this submenu, an item called "link information display" is prepared in addition to the "link setting" described above.

When the designer selects “display link information”, CLM 109 determines that a list display of link information related to text button 520 on card 522 selected immediately before is requested (step S2).
3).

In this case, the CLM 109 generates a screen image of a link information list relating to the text button 520, and generates a link information list window 501 as shown in FIG.
Is displayed (step S24). At this time (that is, in the initial state in which the link information list window 501 is displayed), the link information list window 501 is in a state equivalent to that when the link destination list tab 504 is clicked.
, A link destination list page 502 is displayed. Link name list 5 of this link destination list page 502
In 06, a list of link names of links from which the object (the text button 520 in this case) selected on the card 522 is a link source is displayed.

At the same time, the CLM 109 operates as the text button 5
20 to a text button (link destination text button) 524 which is a link destination component of the text button 520
a and 524b, the links and the arrows (link lines) 526a and 526b indicating the directions thereof are displayed (step S
25 to S27), a text button (link source text button) 52 which is a link source component of the text button 520.
5 displays a link and an arrow (link line) 527 indicating the direction of the link on the text button 520 (step S).
28-S30).

As described above, in the present embodiment, when the designer (user) requests “link information display” in a state where an arbitrary part on the card is selected, that is, a request to display a list of link information on the selected part is made. Then, a link information list window 501 is displayed, and when a link is provided between components on the same card including the component, a link and an arrow indicating the direction are displayed between the components. If there is a link from the component selected by the designer to another card (step S31,
S32) If the linked card is not displayed,
The card is displayed by the CLM 109 (steps S33, S34). In the example of FIG. 5, if a link from the text button 520 to the card 528 is provided, and the card 528 is not being displayed, the link information list window 501 is displayed and the card 528 is displayed at the same time. Is displayed.

Now, with the link destination list page 502 displayed on the link information list window 501,
When the designer clicks the link source list tab 505, C
The LM 109 switches and displays the link destination list page 502 to the link source list page 503. The link name list of the link source list page 503 includes the object selected on the card 522 (here, the text button 52
A list of link names of links to which 0) is a link destination is displayed. Conversely, if the link destination list tab 504 is clicked while the link source list page 503 is displayed,
From link list page 503 to link destination list page 50
The display is switched to 2.

As described above, in a state where the link destination list page 502 or the link source list page 503 is selectively displayed, for example, when the link destination list page 502 is displayed, the designer operates on the page 502. When a desired link name is clicked and selected from the link name list 506, the CLM 109 reads from the memory 106 the attribute information (link destination component type, link destination component name, event, message) of the link of the link name, and reads the attribute information. It is displayed in the areas 508 to 511 on the page 502 (step S
35, S36). At the same time as displaying the attribute information, the CLM 109 highlights the link source object (here, the text button 520) of the corresponding link and the link destination object (step S37). Here, if the link destination object is a component, for example, the text button 524a or 524b, the text button 524a or 524b is highlighted, and if the link destination object is a card, for example, the card 528, the corresponding object corresponds to the card 528. Card icon 532
Is highlighted. In the present embodiment, a method of changing colors and displaying is applied to the highlighting, but it is also possible to add a special mark to display. When the link source and the link destination are component objects on the same card, an arrow (526a, 526b, or 527) indicating a link is also highlighted. If the link source and the link destination are component objects on the same card, only one of the link source and the link destination objects or the arrow representing the link may be highlighted.

(4-2-3) Link Deletion In this embodiment, the created link can be deleted on the link information list window 501. The link deletion procedure will be described with reference to the flowcharts of FIGS. 10 to 12 as an example in a case where the link destination list page 502 is displayed on the link information list window 501 in FIG.

First, the designer sets the link destination list page 502
Click and select the link name of the link to be deleted from the link name list 506 (step S3)
5). Then, as described above, the CLM 109 stores the attribute information of the link having the link name selected by the designer in the area 50.
8 to 511, and highlights the link source and link destination objects of the link (step S3).
5 to S37). This allows the designer to check on the screen the information of the link that he / she has selected to delete, and then clicks the “Delete Link” button 507.

Then, the CLM 109 deletes the link (information) of the link name selected by the designer from the memory 106 and hides the link name in the link name list 506 (steps S38 to S40). At the same time CLM
Reference numeral 109 also hides the corresponding link and the arrow indicating its direction.

When the designer clicks the "close" button 515 provided in the link information list window 501, the CLM 109 hides the link information list window 501 (steps S41 and S4).
2).

In the present embodiment, link setting and deletion can be performed as described above.

However, in such a link setting method, when a certain object receives a message and sends a message to another object, it is necessary to establish a number of links.

For example, in FIG. 6A, when the text button 601A is pressed, the image component 602A is hidden, and when the image component 602A is hidden, the image component 602B is displayed, and the text button 601B is displayed.
If you want the same behavior to occur when you press, you must make a number of links as follows:

First, a link 604 is displayed from the text button 601A to the image part 602A with a "non-display" message.
A is set, and then a link 605A is displayed from the text button 601A to the image part 602B with a “display” message.
Set. Similarly, a link 604 is displayed from the text button 601B to the image component 602A with a message “Hide”
B is set, and then a link 605B is displayed from the text button 601B to the image component 602B with a “display” message.
Set.

In order to simplify such a link setting,
The present inventors separately create an event indicating that the object has been called, separately from the event set for the object, and for example, a “hidden” message is passed to the object (“not displayed”). If "displayed"), a mechanism is proposed in which an event "non-displaying" enters the object.

In the present embodiment, the event creation function includes a manual event creation function for creating an event designated by a designer and an automatic event creation function for automatically creating an event when a link is set (the event is passed to the link destination object). When a message is specified by the designer, if there is no event indicating that the specified message is called, an automatic event creation function for automatically creating the event is provided. Therefore, the manual event creation will be described first.

(4-2-4) Manual Event Creation In general, events such as “pressed”, “released”, and “clicked” are prepared as standard for part objects such as text buttons and image parts. ing. These component objects can receive messages such as “display” and “non-display”.

Therefore, in the present embodiment, for example, “display” is performed from a certain part object to the linked part object.
If a message is sent, the "displayed" event enters the linked part object and the "hidden"
If the message was sent, create an event to include the "hidden" event.

In the following, regarding the event creation, an example of creating an event when a “non-display” message is transmitted to a certain image part will be described with reference to the screen example of FIG.
This will be described with reference to the flowchart of FIG.

When manually creating an event, the designer first operates the design-time data input device 102 (the mouse therein) to select an event from the component objects arranged on the card 202 shown in FIG. Click and select the part object you want to create. Here, it is assumed that a certain image component is selected. The selected image component is called an image component A.

Next, the designer operates the CLMM 207 shown in FIG.
Move the cursor to the "Information setting" item and click on it, and select the submenu corresponding to the "Information setting".
It is displayed by M109. This submenu contains:
Items such as "manual event setting" and "automatic event setting" are provided. Then, when the designer selects “manual event setting” (“manual event setting mode”), C
The LM 109 displays an event list window 701 as shown in FIG. 7 (Step S51).

In the event list window 701, an event name list 702 is arranged. The event name list 702 is used to indicate the event of the component object (here, the image component A) which is the object of the “manual event setting” selected by the designer. A list is displayed. FIG. 7 shows a state in which event names “pressed”, “released”, and “clicked” are displayed.

In the event list window 701,
A create button 703, a delete button 704, and a close button 705 are arranged. When a designer wants to create a new event, the designer clicks a create button 703. Then, the CLM 109 displays an event setting dialog 706 as shown in FIG. 7 (steps S52 and S52).
53).

The event setting dialog box 706 includes a message selection area 707 for selecting a message name.
And event name input area 7 for inputting an event name
08, an OK button 709, and a Cancel button 710.

The designer sets the event setting dialog 706
By clicking a list call button 707a in the upper message selection area 707, a message list (not shown) including message names such as "display" and "non-display" is displayed, and a desired message name (here Then, “non-display” is selected and set in the area 707. Further, the designer inputs and sets a desired event name (here, “not displayed”) in the event name input area 708. As described above, the designer selects the message selection area 707
Of the message name in the event name input area and the event name in the event name input area 708 (step S5).
4).

When the above settings are completed, the designer clicks an OK button 709. Then, the CLM 109 displays a “non-display” event indicated by the event name “hidden” input by the designer in the event name input area 708 (that is, an event indicating that the “non-display” message has been called).
Is newly added in the memory 106 to the image part A, which is a part object specified by the designer, in association with the message (“non-display” message) selected and set by the designer in the message selection area 707, and the event The name “not displayed” is additionally displayed in the event name list 702 (steps S55 and S56).

If the designer wants to delete the added event, the designer operates the mouse to change the event name list 70
2 Select the corresponding event name on the
Click. Then, the CLM 109 deletes the event of the event name selected by the designer from the memory 106 and hides the event name in the event name list 702 (Steps S57 to S59).

The link setting for executing the above example using the event created as described above will now be described with reference to FIG.
This will be described with reference to FIG.

The image part 602A in FIG.
However, the point different from FIG. 6A is that, when the “non-display” message is sent and hidden (the non-display is executed), the “non-display” message is included so that the “hidden” event is included. Is generated (set) in response to the event.

In this case, the designer first sets a link 614A from the text button 601A to the image component 602A by a "non-display" message. Similarly, a link 614B is set from the text button 601B to the image component 602A with a "non-display" message. And the designer
A link 615 is set from the image component 602A to the image component 602B with the "hidden" event and the "display" message so that the image component 602B is displayed after the image component 602A is hidden (the non-display is executed). .

As described above, the "non-display" event is set in the image part 602A in response to the "non-display" message. Therefore, the text component 601A or 601B can be
When a "non-display" message is sent to 2A and the image component 602A is non-displayed, a "non-display" event occurs. Then, a “display message” is sent from the image component 602A to the image component 602B to which the link 615 is set by the “hidden” event and the “display” message between the image component 602A. Will be displayed.

(4-2-5) Automatic Event Setting Next, automatic event creation for automatically creating / deleting an event will be described with reference to the flowcharts of FIGS.

If you want to create / delete an event automatically,
The designer sets “information setting” in the CLMM 207 shown in FIG.
Is moved to the item and clicked, a submenu corresponding to the "information setting" is displayed by the CLM 109, and "automatic event setting" (instead of "manual event setting" described above) is displayed from this submenu. "Automatic event setting mode"). By selecting this "automatic event setting", it is possible to set so that an event is automatically created / deleted as described below. That is, by using this function, when the designer specifies a desired part object as a link destination and specifies a desired message sent to the object,
An event corresponding to the message can be created automatically. When this is applied to the example of FIG. 6B, the following is obtained.

First, it is assumed that the designer has set the link 614A from the text button 601A to the image component 602A by a "non-display" message. In this case, as shown in the flowchart of FIG. 14, if the "automatic event setting" mode is set (step S71) and there is no event corresponding to the message (here, the "non-display" message) (step S71). S72), CLM1
09 automatically creates an event (here, an event “hidden”) corresponding to the message (“hidden” message) for the image component 602A (step S73), and updates the event list (step S73). S74).

In this state, the designer clicks the "non-display" button on the image component 602A by pressing the other text button 601B.
It is assumed that the link 614B is set in the message. At this time, since an event of “not displayed” has already been created in the image component 602A in response to the “not displayed” message (step S72), the CLM 109 performs processing so as not to create a duplicate. That is, CLM
109 is a step for creating an event corresponding to the “non-display” message S73 and an event list updating step S73
Go through 74.

In the "automatic event setting" mode, unnecessary events are automatically deleted. This is shown in FIG.
When applied to the example of (b), the following is obtained.

First, the designer sets a link 614 from the previously set text button 601A to the image component 602A.
It is assumed that A has been deleted. In this case, the CLM 109
It is determined according to the flowchart of FIG. 15 (steps S81 and S82 in FIG. 15) whether to delete the event corresponding to the message used for the deleted link.

That is, if the message is in the "automatic event setting" mode (step S81) and is used for the deleted link (here, link 614A) (here, the "non-display" message) If the link is not used (step S82), CLM1
09 automatically deletes the event (the event "hidden") created for the image component 602A in response to the message (the "hidden" message) (step S83), and updates the event list. (Step S84).

However, in FIG. 6B, a link 614 from the text button 601A to the image part 602A is used.
At the stage when A is deleted, the link 614B from the other text button 601B to the image part 602A is still
Does not exist, the event of "hidden" corresponding to the "hidden" message used for link 614A for image part 602A is not deleted.

In this state, the designer sets the text button 60
If the link 614B from 1B to the image component 602A is also deleted, there is no other link corresponding to the “hidden” event, so the CLM 109 automatically deletes the “hidden” event (steps S81 to S81). S
83).

Now, as in the above example, the text button 601A and the image part 602A in FIG.
When the “hidden” event created for the image component 602A is automatically deleted as a result of deleting the link 614A to the image component 602A and the link 614B from the text button 601B to the image component 602A, the event is deleted. A link 615 from the used image component 602A to the image component 602B cannot exist. Therefore, when a certain event is automatically deleted, if there is a link using the event as shown in the flowchart of FIG.
91), and automatically delete the link using the event (step S92).

(5) Description of Prototype Execution Operation Finally, the UI design apparatus shown in FIG.
The prototype execution operation 3) will be described. This prototype execution operation is performed by the UI according to the instructions from the designer.
This is executed by the prototype execution unit 108 in the design mechanism 103. The state where the prototype is being executed is called a prototype execution mode.

In the prototype execution mode, the processing of data designed by the editing unit 107 is all handled by the prototype execution unit 108. In the design mode (while the editing unit 107 is running), the CLM 109 in the editing unit 107 manages data as described above. In the prototype execution mode, the PTM (prototype manager) 111 in the prototype execution unit 108 Manages data.

To switch from the design mode to the prototype execution mode, the designer operates the design-time data input device 102 (middle mouse) to operate the CLM shown in FIG.
The cursor may be moved to the item "execute prototype" in M207, clicked, and the "execute prototype" may be selected. In this case, the CLM 109 is a PTM 111
Start As a result, the PTM 111 has a prototype manager menu (PTMM) 801 as shown in FIG.
Is displayed on the display of the output device 101. This PT
The MM 801 is displayed while the PTM 111 is running. PT
The MM 801 has items “prototype execution”, “prototype suspension”, and “prototype end”.

In the prototype execution mode, when the designer operates the simulation input device 104 (middle mouse) and selects “prototype execution” from the PTMM 801, the PTM 111 communicates with the hardware device in the simulation input device 104. Is performed, and the data input from the hardware device is used to execute the P
An event is given to the corresponding object via TM111. As a result, a prototype (simulation) is executed.

On the other hand, when “prototype suspension” is selected from the PTMM 801, the PTM 111 switches to a state of not accepting an input from a hardware device.
Suspend prototype execution. If “prototype execution” is selected again in this state, the PTM 111 is released from a state in which an input from a hardware device is not accepted. Thus, the prototype is executed again.

Next, when “prototype end” is selected from the PTMM 801, the PTM 111
Is notified of the termination. Then CLM109 is PTM11
1 and the PTM 111 terminates the PTMM 801. When the PTMM 801 ends, the mode is switched to the design mode again.

The above-described UI design method applied in the UI design mechanism 103 of the UI design apparatus is effective for an authoring tool for designing an operation process using a link.

[0133]

As described in detail above, according to the present invention, a list of event names of events that can receive a user-specified link source object, a list of message names of messages that can receive a user-specified link destination object, Is automatically displayed, from which the user simply selects and specifies the desired event name and message name, and the event of the link source object of the event name selected and specified by the user and the link destination object of the message name selected and specified by the user A link with an attribute that includes a message to is automatically set, so complex events and messages can be set easily.

Further, according to the present invention, the user selects and specifies from the list the message name of a message that can receive the specified object, and specifies the event name of a new event indicating that the message has been called. By simply inputting, it is possible to create an event having an event name specified and input by the user and indicating that a message having a message name selected and specified by the user has been called. Thus, when a message of a certain object is called and a message is to be transmitted to another object, the operation can be designed with a simpler link setting.

Further, according to the present invention, when the user specifies a link destination object and a message to be passed to the object for setting a link, it is determined whether or not there is an event indicating that the message specified by the user has been called. Therefore, a new event indicating that a user-specified message has been called is automatically created and added to the user-specified object. The operation design when a message is desired to be transmitted can be made simpler with simpler link settings.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a user interface (UI) design device according to an embodiment of the present invention.

2 is a card layout manager menu (CLMM) 20 displayed when the UI design apparatus in FIG. 1 is started up.
7 and Card Layout Manager window (CLM
FIG. 14 is a diagram showing an example of a screen image including W) 201.

FIG. 3 is a view showing an example of a screen image including a text button information setting dialog 301 when a text button is created.

FIG. 4 is a view showing an example of a screen image including a link setting dialog 402 at the time of link setting.

FIG. 5 is a view showing an example of a screen image including a link information list window 501 when a link information list is displayed.

FIG. 6 is a diagram for explaining an example of a link setting method realized by preparing an event indicating that a message of the component is called for a certain component, in comparison with a conventional link setting method.

FIG. 7 is a view showing an example of a screen image including an event list window 701 in a manual event setting mode.

FIG. 8 is a view showing an example of a prototype manager menu (PTMM) 801 displayed in a prototype execution mode.

FIG. 9 is a flowchart illustrating a link setting process.

FIG. 10 is a diagram showing a part of a flowchart for explaining a link information list display process.

FIG. 11 is a diagram showing another part of the flowchart for explaining the link information list display processing.

FIG. 12 is a view showing the rest of the flowchart for explaining the link information list display processing.

FIG. 13 is a flowchart illustrating an event creation process in a manual event setting mode.

FIG. 14 is a flowchart for explaining an automatic event creation process when setting a link.

FIG. 15 is a flowchart for explaining an automatic event deletion process when deleting a link.

FIG. 16 is a flowchart for explaining automatic link deletion processing at the time of event deletion.

[Explanation of symbols]

103: User interface design mechanism (UI design mechanism) 105: Database (DB) 106: Memory 107: Editing unit 108: Prototype execution unit 109: Card layout manager (CLM, link setting reception means, event list display means, message list) Display means, event selection means, message selection means,
Link setting means, event name input means, event creation means, event addition means, event deletion means, event presence / absence determination means, automatic event creation means, link deletion means,
Link presence / absence determination means, automatic event deletion means, link search means, automatic link deletion means) 110 parts manager 205, 408, 523 map viewer 402 link setting dialog 404 event selection area 405 message Selection area 417 ... Event list 501 ... Link information list window 502 ... Link destination list page 503 ... Link source list page 701 ... Event list window 702 ... Event name list 706 ... Event setting dialog 707 ... Message selection area 708 ... Event name input area

Claims (10)

[Claims] 1. An operation is designed by arranging various component objects at arbitrary positions on a screen object representing an operation screen of a user interface and linking the arbitrary component objects to other objects. In the user interface design device, a link setting receiving unit that receives designation of a link source object and a link destination object to be linked by a user operation, and an event of an event in which the link source object received by the link setting receiving unit is received. Event list display means for displaying a list of names; message list display means for displaying a list of message names of messages that can be received by the link destination object received by the link setting receiving means; and the event list table An event selecting unit that receives a selection designation of an event name by a user operation from a list displayed by the unit; a message selection unit that receives a selection designation of a message name by a user operation from a list displayed by the message list display unit; Link setting means for setting a link having an attribute including an event of the link source object having the event name accepted by the event selecting means and a message to the link destination object having the message name accepted by the message selecting means. A user interface design apparatus characterized in that: 2. Designing an operation by arranging various component objects at arbitrary positions on a screen object representing an operation screen of a user interface and linking the arbitrary component objects to other objects. In the user interface design device, a message selection means for receiving a message selection designation by a user operation from a list of message names of messages for which a user-specified object can be received, and a message having the message name received by the message selection means are called Event name input means for accepting an input by a user operation of an event name of an event to be newly generated separately from an event previously set in the user-specified object, and An event creating means for newly creating an event having a specified event name and indicating that a message having the message name accepted by the message selecting means has been called; and an event created by the event creating means, An event adding means for additionally setting a list of events in which a specified object can be received. 3. An event list display means for displaying a list of event names of events for which a user-specified object can be received, and an event of an event to be deleted by a user operation from the list of event names displayed by the event list display means. 3. The system according to claim 2, further comprising: an event selection unit that receives designation of a name selection; and an event deletion unit that deletes an event having the event name received by the event selection unit from the event list.
User interface design apparatus according to the above. 4. An operation is designed by arranging various part objects at arbitrary positions on a screen object representing an operation screen of a user interface, and linking the arbitrary part objects to other objects. In the user interface design device, if a link destination object and a message passed to the object for linking are specified by a user operation, whether an event indicating that the user-specified message has been called already exists. An event presence / absence determining means for determining whether or not the event has occurred; and an automatic event for newly creating an event indicating that the user-specified message has been called and adding the event to the user-specified object according to the determination result of the event presence / absence determining means Characterized by comprising event creation means. Interface design apparatus. 5. A link deletion unit for deleting a link specified by a user, and it is determined whether or not a link deleted by the link deletion unit and a link destination object and a message passed to the object have the same link. It further includes a link presence / absence determination unit, and an automatic event deletion unit that deletes an event indicating that the message passed to the link destination object has been called, according to a determination result of the link presence / absence determination unit. The user interface design device according to claim 4, wherein 6. An event deletion unit for deleting an event specified by a user, a link search unit for searching for a link using the event deleted by the event deletion unit, and a link searched by the link search unit. 6. The user interface designing apparatus according to claim 4, further comprising an automatic link deleting unit. 7. An operation is designed by arranging various part objects at arbitrary positions on a screen object representing an operation screen of a user interface, and linking the arbitrary part objects to other objects. In the user interface design method, a specification by a user operation of a link source object and a link destination object to be linked is received,
A list of event names of events that the link source object can receive and a list of message names of messages that the link destination object can receive are displayed, and an event name according to a user operation is selected and designated from the displayed list of event names. And an attribute including a message of a link source object of the received event name and a message to a link destination of the received message name. A user interface design method, characterized by setting a link having a name. 8. An operation is designed by arranging various component objects at arbitrary positions on a screen object representing an operation screen of a user interface and linking the arbitrary component objects to other objects. In the user interface design method, a list of message names of messages that can be received by a user-specified object is displayed, and selection designation of a message name according to a user operation from the list is received, while a message having the received message name is called. Accepts an input by a user operation of an event name of an event to be newly generated separately from an event preset in the user-specified object, has the accepted event name, and has the accepted message name Message was called A new event indicating that the user-designated object is received, and adding the created event to a list of events in which the user-specified object can be received. 9. An operation is designed by arranging various part objects at arbitrary positions on a screen object representing an operation screen of a user interface and linking the arbitrary part objects to other objects. In the user interface design method, if a link destination object and a message passed to the object for linking are specified by a user operation, whether an event indicating that the user-specified message has been called already exists. If there is no event indicating that the user-specified message has been called, a new event indicating that the user-specified message has been called is automatically created and the user-specified message is generated. User interface design characterized by additional settings for objects Law. 10. An operation is designed by arranging various object parts at arbitrary positions on a screen object representing an operation screen of a user interface, and linking the arbitrary object parts to other objects. A computer-readable recording medium having recorded thereon a program that enables a user to specify a message name in accordance with a user operation from a list displaying a list of message names of messages that can receive an object specified by a user. Accepting, and accepting an input according to a user operation of an event name of an event to be newly generated separately from an event preset in the user-specified object, indicating that the message with the accepted message name has been called Steps and the accepted event Creating a new event indicating that the message with the received message name has been called, and adding the event to a list of events in which the user-specified object can be received. Recorded computer-readable recording medium.