JP3288939B2 - Screen transition control device - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention creates a screen transition process that can manage the screen transition process in a unified manner when creating a screen transition process in data processing using an event-driven programming method. The present invention relates to a screen transition control device. The present invention also relates to a screen transition control device that visually creates a screen transition process.

[0002]

2. Description of the Related Art Conventionally, as a programming language for realizing an event-driven programming method, for example,
Visual Basic language ("Visual Ba
"sic" is a registered trademark of Microsoft Corporation). In the Visual Basic language, various parts (controls) are attached to a screen used for data processing to generate a screen, and the parts are operated in response to an event (an event such as a mouse click, key input, or command selection). This is a so-called event-driven programming method that employs a method of programming a process to be performed. FIG. 28 shows a conventional method for creating a screen transition process. In FIG. 28, a screen 1 900 is composed of a component 1 902, a component 2 903, a component 3 904, and a component 4 905, which are buttons 1. When a part 1 902 as a button 1 is pressed, the screen changes to a screen 2 901. In the Visual Basic language, screen transition processing is described for each component. For example, in FIG. 28, when the component 1 902 which is the button 1 of the screen 1 900 is pressed, the screen changes to a screen 2 901. For this reason, the screen transition processing is programmed in a pressed event portion executed when the component 1 902 as the button 1 is pressed.

[0003]

As described above, in the conventional event-driven programming system, a screen transition process is described for each component attached to the screen. For this reason, there is a problem that the screen transition processing cannot be centrally managed. Further, when the screen transitions from one screen to a plurality of screens, there is a problem that it is difficult to grasp the flow of the entire screen transition. Also, when changing a given screen to another screen, it is necessary to investigate each part of each screen to determine from which part of which screen the changed screen is programmed. Had a problem with maintainability.
Further, the fact that the screen transition processing cannot be centrally managed has a problem that it is difficult to visually represent the flow of the entire transition.

[0004] The present invention has been made to solve the above-mentioned problem, and integrally manages screen transition processing. Also, a screen transition process is visually created. further,
Visually represent the created screen transition process.

[0005]

A screen transition control device according to the present invention has the following elements. (A) a processing module creation unit creates a processing module used for data processing by using an event-driven programming method; (b) a screen creation unit creates a plurality of screens used for the data processing; c) a screen transition module creation unit creates a screen transition module that controls the transition of the plurality of screens, and (d) an execution unit controls the transition of the plurality of screens based on the screen transition module. Data processing is performed using the processing module.

[0006] Further, the screen transition module creating unit includes:
The screen transition module is automatically created from a flowchart.

[0007] Also, the flow chart drawing drawing provided in the screen transition module creator includes a part indicating a start of processing, a part indicating display of a screen, and a part indicating branching of processing according to predetermined conditions. In addition to creating and drawing a flowchart of a screen transition visually representing a screen transition process, a combination of the above-described five flowchart components of a component signifying that the process is unconditionally branched and a component signifying the end of the process, An instruction generation unit included in the screen transition module generation unit decodes the flow chart of the screen transition and generates a screen transition control instruction corresponding to the flowchart component.

Further, the processing module creating section creates a screen erasing module for erasing a displayed screen as one of the processing modules.

The screen erasing module includes an erasing instruction for erasing the screen and a screen transition number setting instruction for outputting a screen transition number for selecting a screen to be displayed next to the screen transition module. The screen transition module inputs the screen transition number and selects and displays the next screen to be displayed based on the screen transition number.

Further, the processing module creating section automatically generates the erase command and the screen transition number setting command.

[0011]

BEST MODE FOR CARRYING OUT THE INVENTION

Embodiment 1 FIG. Hereinafter, an example of the screen transition control device of the present invention will be described with reference to the drawings. FIG. 1 is a diagram showing one configuration of the screen transition control device of the present invention. 1, the screen transition control device includes a processing module creating unit 1, a screen creating unit 7, a screen transition module creating unit 10, and an executing unit 17. The processing module creation unit 1 creates a processing module used for data processing using an event-driven programming method. In the first embodiment, the event-driven programming language Visual
Use Basic. The processing module creation unit 1 includes a processing module A2 and a processing module B used for data processing.
3 and a screen erasing module 4 for erasing a screen used for data processing. Further, the screen erasing module 4 includes a screen transition number setting instruction 5 and an erasing instruction 6 in the module. The screen transition number is a number for selecting a screen to be displayed next. The screen transition number setting instruction 5 is an instruction for setting a screen transition number when a button for starting transition to the next screen is clicked.
Further, the delete command 6 is a command for deleting the currently displayed screen before transitioning to the next screen. The screen creation unit 7
Creates a screen form to be used in screen processing. For example, assuming that the screen 1 and the screen 2 are used in the data processing, the screen creation unit 7 creates the form of the screen 18 and the form of the screen 29. In the first embodiment, the Visu
Since al Basic is an event-driven programming language, the form of screen 1 and screen 2 is V
It shall be created based on the specifications of actual Basic. The screen 18 includes a button 18a for transitioning to the screen 29. Conventional Visual
In Basic, screen 29 is displayed for button 18a.
The process of transitioning to was programmed. In the screen transition control device according to the present invention, the button 18a is set with the form name of the screen to which the transition is made and the command to erase the current screen using parameters. The setting method will be described later in detail. Further, the screen transition module creating unit 10 creates a screen transition module that controls the transition of a plurality of screens. The creation is performed by drawing a flowchart using flowchart components. For this purpose, the screen transition module creation unit 10 includes a flowchart diagram creation drawing unit 11. Then, based on the flowchart created by the flowchart diagram creating / drawing unit 11,
The instruction generator 12 generates an instruction. In the first embodiment, since Visual Basic is used as an example,
The instruction generated by the instruction generation unit 12 is Visual Bas
It is an instruction based on the specification of ic. The screen transition module 13 created by the screen transition module creation unit 10 includes a command 14 for displaying a screen and a screen transition number determination process 15 for determining a transition to the next screen.
For example, in a process of transitioning from screen 1 to screen 2 using screen 1 as a reference screen, the screen transition module 13 includes a screen 1 display instruction 14 and a screen transition number determination process 15. The screen transition number determination processing 15 includes a screen 2 display instruction 16 for displaying the screen 2 in the determination processing. The execution unit 17 follows the screen control flow described in the screen transition module 13 and
9, the processing module A2, the processing module B3, and the screen erasing module 4 are executed.

FIG. 2 shows a screen displayed when the flowchart drawing / drawing unit is started. In FIG. 2, the flowchart diagram creating / drawing unit 11 develops a flowchart on the work area 20. Then, the flowchart is created using the flowchart parts group 21. The flowchart part group 21 shows parts of a flowchart that can be used. In the first embodiment, usable flowchart components are an arrow 22, a start terminal 23, a screen display component 24, a branch component 25, a jump component 26, and an end terminal 2.
7 and a connection line 28. The user visually creates a screen transition module using these flowchart components. Specific examples of the screen transition module created using these flowchart components will be described in detail with reference to another drawing.

FIG. 3 is a diagram for explaining the processing contents indicated by the flowchart components. In FIG. 3, a start terminal 23 indicates an initialization process. In the initialization process, get the argument passed from outside. The screen display component 24 displays a Form (screen) in a modeless manner. Modeless display means Fo
After displaying rm (screen), the following VisualBasi
Indicates that the code of c is executed in order. Visual
There is a code "Show" in the Basic code. This is a code for displaying the form.
In the first embodiment, the Visual Basic
Instead of using “Show”, a form is displayed using “FormShow” in the screen transition control device of the present invention.A description of “FormShow” will be described later in detail. 2
4 is a process of waiting until the Form is closed, and an Unlo obtained by acquiring the Unload comparison value.
There is a process for returning an ad comparison value as a return value. Unload
The comparison value is a comparison value for determining whether or not the displayed screen is to be deleted. Since the value is set by the screen deletion module 4, the screen display component 24 has the value set by the screen deletion module 4. To get. The branch component 25 compares the return value acquired by the screen display component 24 with the branch condition. The user registers the branch condition in the branch part 25 as a branch parameter. The setting method and setting contents of the branch parameter will be described later in detail. Further branch parts 25
Branches the process based on the result of the comparison. The jump component 26 jumps to a target Label. Labe
1 is a label in Visual Basic. The target Label is registered by the user as a jump part parameter. The method of setting the jump part parameters will be described later in detail. The termination terminal 27 performs termination processing.

FIG. 4 is a diagram showing a source generated from each flowchart component. The source is Visual B
Asic specifications. The instruction generation unit 12 generates a source as shown in FIG. 4 for each component provided in the flowchart diagram creation / drawing unit 11. In FIG. 4, the underlined code is a portion that can be changed by the user.

FIG. 5 is a flowchart showing a processing procedure performed by the user in order to use the screen transition means control device. As shown in FIG. 5, the user first creates a screen form (S1). Form is created using the conventional Visual B
The method and procedure are the same as those performed in the asic. Further, in the process of S1, Form No of each screen is determined. Next, a screen transition module is created (S2). The screen transition module is generated by the flowchart creation / drawing unit 11 using the flowchart parts group 21 shown in FIG. FIG. 6 is a screen transition diagram used to describe a specific example of creating a screen transition module. As shown in FIG. 6, the screen 118 changes to a screen 219 when the “I like this” button is clicked. Clicking the “I do not like this” button on the screen 118 displays a confirmation screen 80.
If the user clicks the “Yes” button on the screen 219, the screen returns to the screen 118. Further, on the confirmation screen 80, when the “Yes” button is clicked, the processing is completed, and when the “No” button is clicked, the screen returns to the screen 118. The user selects the screens 118 and 21 shown in FIG.
9 and the confirmation screen 80 which is the main processing screen 11
A screen transition module is created for the screen transition process between the screen transitions 8 and 219. The confirmation screen 80 is positioned as a sub-screen in the screen transition control device of the present invention. The sub screen is a screen displayed by a screen transition from the main processing screen, but is not a screen of completely different processing, but a screen of a sub processing having an intermediate processing role for the main processing. The method of creating the confirmation screen 80 and the display determination will be described later in detail.

The creation of a screen transition flowchart for screens 118 and 219 in FIG. 6 will be described below.
The flowchart diagram creation / drawing unit 11 uses Visual Ba
From the add-in menu of sic4.0, select “Draw Flowchart Diagram” to create a flowchart diagram drawing unit 1
Start 1 FIG. 7 shows a pull-down menu including “flowchart diagram creation drawing” displayed by selecting the add-in menu. When "Draw Flowchart Diagram" is selected from the pull-down menu shown in FIG. 7, the main window 30 for creating the screen transition flowchart shown in FIG.
Is displayed. The user selects necessary flowchart components from the flowchart component group displayed in the component window 38 and draws a flowchart in the work area 32.

FIG. 9 is a flowchart created in accordance with the flow of the main processing of the screen transition shown in FIG. The user sequentially selects the flowchart components of S11 to S16 shown in FIG. 9 and arranges the flowchart components in the work area 32 in an arrangement as shown in FIG. The parameters displayed in the components of S12 to S15 in FIG. 9 are parameters. When parameters are set for each component, they are displayed as shown in FIG. The setting of the parameters is performed after the parts are arranged in the work area.

Next, a method of setting parameters for each component will be described. First, the parameter setting of the screen display component 24 will be described. The user is in the work area 3
The mouse is placed on the screen display component 24 from the flowchart components arranged in FIG. 2 as shown in FIG. Alternatively, “parameter setting (T)” is selected from the setting menu 40 of FIG. 10B displayed by clicking the setting menu of the main window 30. Then, the display component parameter setting screen 41 shown in FIG.
Is displayed. In the display component parameter setting screen 41,
There is a form name text box 42 for inputting a Form name displayed on the screen display component 24 and a Japanese name text box 43 for inputting a Japanese name. Further, there are a setting button 44 and a cancel button 45. Clicking the Cancel button 45 displays the display part parameter setting screen 4
1 is deleted, and the main window 30 is displayed. When the setting button 44 is clicked, the information entered in the form name text box 42 and the Japanese name text box 43 is determined. Form name text box 42
Is displayed as a list of the form names set in the name property in Visual Basic. The user selects a corresponding form name from the list of form names and displays the form name text box 42. Set to. In the Japanese name text box 43, the user can input an arbitrary Japanese name. In the Japanese name text box 43,
Form set in form name text box 42
It is also possible to acquire and display the name set in the Caption property of the name. For example, when "Form1" is set in the form name text box 42, "Screen 1" is set in the Japanese name text box 43, and the setting button 44 is clicked, as shown in S12 of FIG. “Screen 1” is displayed on the screen display component 24. Also, the display component parameter setting screen 41 is displayed by double-clicking the screen display component 24 in S14 of FIG.
When “m2” is set and “screen 2” is set in the Japanese name text box 43 and then the setting button 44 is clicked, the set parameters are displayed on the screen display component 24 as shown in S14 of FIG.

Next, the parameter setting of the branch part 25 will be described. The user places the mouse on the branch component 25 in the flowchart components arranged in the work area 32 and double-clicks the mouse. Alternatively, the user selects "Parameter Setting (T)" from the setting menu 40 of FIG. 10B displayed by clicking the setting menu of the main window 30. Then, a branch parameter setting screen 50 of FIG. 12 is displayed. In the branch parameter setting screen 50 of FIG.
Branch style 5 for specifying YES / NO branch style
1, an unload comparison value combo box 52 for specifying an unload comparison value, and a Japanese name text box 53 for specifying a Japanese name to be displayed on the branch part 25 in FIG.
And a setting button 54 and a cancel button 55.
When the cancel button 55 is clicked, the branch parameter setting screen 50 is deleted, and the main window 30 is displayed. When the setting button 54 is clicked, the set parameters are registered. The branch style 51 has six types of styles. Each branch style is shown in FIG.
This corresponds to the flowchart of FIG. S13 in FIG.
13 matches the branch style shown in FIG. In the unload comparison value combo box 52, a screen transition number for selecting a screen to be displayed next is input.
On the screen 1 in FIG. 6, when the “I like this” button is clicked, the screen transits to the screen 2. Therefore, the same value as the unload comparison value set in the “I like this” button on the screen 1 is designated in the unload comparison value combo box 52. The unload comparison value set on the “I like this” button on the screen 1 will be described later in detail. The specified value is not displayed in the flowchart of FIG. In the Japanese name text box 53, a Japanese name to be displayed on the branch part 25 in S13 of FIG. 9 is input. Here, "I like the button?"

Next, the parameter setting of the jump part 26 will be described. The user moves the mouse to the jump part 26 in the flowchart parts arranged in the work area 32 and double-clicks. Or, main window 3
FIG. 10 displayed by clicking the setting menu of 0
"Parameter setting (T)" is selected from the setting menu 40 of (B). Then, a jump part parameter setting screen 56 of FIG. 14 is displayed. The part name text box 57 is displayed on the jump part parameter setting screen 56.
And a setting button 58 and a cancel button 59. In the part name text box 57, the Japanese name set for the part to which the user jumps is specified.
Are displayed in a list, and the user selects the corresponding Japanese name and inputs it to the component name text box 57. When the setting button 58 is clicked, the set component name is determined, and “screen 1” is displayed in S15, which is the jump component 26 in FIG. In the flowchart of FIG. 9, there are other start terminals 23 and end terminals 27, but it is assumed that no parameters are set for these two terminals. Arrow 22
Indicates the processing direction of each component, and since the connection line 28 is a line for connecting each component, no parameter is set.

After setting parameters for each component in the flowchart of FIG. 9, the user generates a screen transition module based on the flowchart. The module is generated by clicking “File (F)” in the main window 30 and displaying the file menu 29 shown in FIG.
Is performed by selecting "Generate (G)" from. When “Generate (G)” is selected, the instruction generation unit 12 is activated, and each component in the flowchart of FIG. 9 is developed by the instruction generation unit 12 according to the generation source shown in FIG. FIG. 16 shows a screen transition module created by expanding the flowchart of FIG. 9 according to the generation source of FIG. As shown in FIG. 4, the instruction generation unit 12 attaches a Label to each component in the flowchart, and generates a source such that the processing of each component is closed for each Label. Closed means the GoTo prepared at the end of processing of each part
This means that the processing jumps to the processing of the target component by the instruction. However, the start terminal of S11 in FIG.
The termination terminal of 16 is the processing content and the Label for the processing.
Expand l with a fixed source. For example, since the process of S12 in FIG. 9 is a screen display component, the screen display component 2 in FIG.
4 based on the source. First, Label_xx
1 is replaced with the Form name set in the parameter of the screen display component 24. The set Form name is
Since it is "Form1," the Label name is Label_
Form1. However, if there are many screen display components in one flowchart and there are many processes for displaying the same screen, the Lab_Form1 Lab
There are many el. Therefore, the screen display component 2
The identifiers are added after Form1 in the order of appearance of No.4. Accordingly, Label for S12 in FIG. 9 is Label_
Form1_0. Next, a command to display the screen Fo
Expand rmShow xx2. The form name is substituted for xx2. In the parameter setting of the screen display component 24, the form name was “Form1”. For this reason,
FormShow xx2 is FormShow For
m1. Subsequently, Label_xx3 is expanded.
According to FIG. 9, S12 is coupled to the branch component of S13. Assuming that Labels starting with “If” are added to Labels for branch parts, Label_xx3
Becomes Label_If. However, when there are many branch parts in one flowchart, Label_If
Many Labels exist. Therefore, an identifier is added after If in the order of appearance of the branch parts. Then, Label_xx3 becomes Label_If1.
Further, in order to cope with a case where there is a plurality of branch conditions in one branch part, an identifier is further added after Label_If1. Therefore, Label_xx3 is the Label_xx3.
_If_0.

Next, the branch component in S13 is developed in the source. Since the branch part in S13 is combined with the screen display part in S12, the Label of the branch part is Label
It becomes the same Label as _xx3. As the branch condition, the unload comparison value of the previously set branch component parameter is used. For example, if the unload comparison value is set to "1", the branch condition is If FormReturn =
It becomes 1. FormReturn is a variable name of the unload comparison value. Subsequently, the label name Label_xx6 of the jump destination when the branch condition is true (Yes) is expanded. Label_xx6 is the Label name of the part connected to YES in S13. Instruction generation unit 12
Recognizes, based on the style specified in the branch style of the branch parameter, that the image is linked to the screen display component in S14 if the branch condition is YES. For this reason,
The form name in S14 is substituted for xx6 and Lab
el_xx6 is expanded to Label_Form2.
However, when there are a plurality of processes for displaying the same screen in one flowchart, a large number of Labels called Label_Form2 exist. Therefore, an identifier is added after Form2 in the order in which the screen display components 24 appear. Therefore, Label_xx6 is equal to Label_Fo.
rm2_0. Further, the label name Label_xx7 of the jump destination when the branch condition is false (NO) is expanded. Label_xx7 is the Label name of the part connected to NO in S13. According to the branch style, NO is coupled to the end terminal of S16. Label of the end terminal is fixed to Label_End. Therefore, Label_xx7 is expanded to Label_End.

Next, the screen display components in S14 are developed.
The source generated for S14 is developed in the same manner as the source generated for S12. For this reason, La
The label name is Label_Form2_0. Also,
The screen display command is FormShow Form2. Further, the screen display component of S14 is connected to the jump component of S15. Therefore, Label_xx3
Is expanded to the Label name of the jump part. The Label name for the jump component is Label_Jump. However, if there are many jump parts in one flowchart, there will be many Label_Jumps. For this reason, Jump after Jump
Add identifiers in the order in which the parts appear. Therefore, Label
_Xx3 is Label_Jump1. Further, for convenience, _0 is added after Jump1 similarly to the Label name of the screen display component or the branch component. And Ju
Label_Jump is the Label name for the mp part
1_0.

Subsequently, the jump part in S15 is developed. The Label name of the Jump component is Label_Jump1_0 because it is the connection destination of S14. Also, in the parameter setting of the jump part, the name of the part to be jumped is set. Jump parts jump
This is “screen 1”, and screen 1 shows the screen display component of S12. For this reason, Label_xx9 is Label_xx9.
_Form1_0. As described above, the instruction generation unit 12
Expands the source based on the flow chart shown in FIG. 9 according to the generation source shown in FIG. 4 for each part in the flow chart, and generates a screen transition module as shown in FIG.

Up to now, the screen form setting by the screen creation unit 7 and the creation of the screen transition module by the screen transition module creation unit 10 have been described. next,
The registration of processing that occurs when a button provided on each screen is clicked will be described below. FIG. 17 is a flowchart showing a procedure for registering a process generated by clicking a button. FIG. 18A is a diagram showing a part of the form on the screen 1 in FIG. FIG. 18B is a diagram in which a processing module creation unit is selected from a pull-down menu displayed by selecting an add-in in the main menu. FIG. 19 is a diagram showing an event selection screen displayed when processing module creation is selected from the menu of FIG. 18B. FIG. 20 is a diagram showing an operation content setting screen displayed by clicking the selection button in FIG. FIG. 21 is a diagram showing an operation selection screen to be added, which is displayed by clicking the add button in FIG. FIG. 22 is a diagram showing an unload processing setting screen displayed by selecting an unload processing from the additional processing selection list box in FIG. FIG. 23A is a diagram showing the source of the unload processing. FIG.
(B) is a figure which shows the generation source of confirmation message processing. FIG. 24 is a diagram showing a confirmation message processing setting screen displayed by selecting confirmation message processing from the additional processing selection list box of FIG. Below, FIG.
Screen 118 and screen 21 shown in FIG. 6 using FIG.
The setting operation of the unload processing setting and the confirmation message processing setting for the button arranged in FIG. 9 will be described with reference to the flowchart of FIG. The unload process is a process of deleting a predetermined screen and displaying another screen when the screen transitions from the predetermined screen to another screen, and the control of the processing is performed from the predetermined screen to another screen. It refers to the process of completely moving. In the confirmation message process, a screen transitions from a predetermined screen to another screen, but the predetermined screen is not erased and another screen is displayed together with the predetermined screen. Then, even if the screen changes, the control of the processing does not change. Screen 1 in FIG.
The process of transitioning from the screen 18 to the screen 219 is an unloading process, and the process of transitioning from the screen 118 to the confirmation screen 80 is a confirmation message process.

First, processing for the buttons on the screen 118 is set. "I like this" button is on screen 21
9 is an event for transitioning the control of the process to 9. The screen 219 is displayed after the screen 118 is deleted. Therefore, the setting of the unload processing is performed for the “I like this” button. In addition, a “no favorite” button on the screen 118 transits to the processing of the confirmation screen 80. However, when the confirmation screen 80 is displayed, the screen 118 is displayed without deleting the screen 118, and the confirmation screen 80 is displayed at the same time. For this reason, confirmation message processing is set for the “I do not like this” button.

First, the procedure for setting the unload processing for the "I like this" button will be described. FIG.
"I like" button 61 from the screen setting screen 60 of (A)
Is clicked and "Add-in" is selected in the main menu 62 of FIG. If you select "Add-in",
When a pull-down menu 63 is displayed, a process module creation 64 is further selected. When the process module creation 64 is selected, an event selection screen 70 of FIG. 19 is displayed. The event display list box 71 displays events set in the button control. To set a process for the event "when the button is pressed", the "Cl
ic "and click on the select button 72.
When the cancel button 73 is clicked, FIG.
The screen setting screen 60 of (A) is displayed. Select button 7
Clicking on 2 displays an operation content setting screen 87 in FIG. In the continuous processing content list box 81, the added processing is displayed. Here, "(none)" is displayed because the process to be added has not been selected yet. When the add button 82 is clicked, an operation selection screen 90 to be added shown in FIG. 21 is displayed. The processing to be added is performed in the additional processing selection list box 91 of the operation selection screen 90 to be added.
Choose more. In addition, the continuous processing content list box 81
When one of the displayed processes is selected and the edit button 83 is clicked, the selected process content can be changed. When one of the processes displayed in the continuous process content list box 81 is selected and the delete button 84 is clicked, the selected process can be deleted. Further, when the OK button 85 is clicked, the processing displayed in the continuous processing content list box 81 can be determined. When the cancel button 86 is clicked, an event selection screen 70 of FIG. 19 is displayed. Here, in order to add an unload process to the "I like" button 61, the user clicks an add button 82 in FIG. Then, an operation selection screen 90 to be added is displayed, and “unload processing” is selected from the additional processing selection list box 91, and an OK button 92 is clicked. OK button 9
Clicking on 2 displays the unload processing setting screen 100 of FIG. On the unload processing setting screen 100, an unload comparison value is set. The unload comparison value is a value for determining whether or not the screen 118 is deleted and the screen is shifted to the screen 219. The unload processing is performed in the processing module creation unit 1 in the pattern shown in FIG.
Generates the source. According to FIG. 23A, the value set as the unload comparison value is stored in a variable called FormReturn (the value set as the unload comparison value is stored in Number). Although the setting of the branch component parameter described above (FIG. 12) does not refer to the value to be set as the unload comparison value, “1” is set here. When the unload comparison value is set to “1”, the instruction generation unit 12 replaces S13 in FIG. 9 with If FormReturn as shown in S13 in FIG.
n = 1 Then GoToLabel_Form
Expand to 2_0. The above-mentioned form in the branch part 25
Return is a global variable in which a value for determining whether to transition from screen 1 to screen 2 is set. When the “I like” button 61 in FIG. Therefore, in the unload processing for the “I like” button 61, the FormRetu
The unload comparison value is set to "1" so that "1" is set to rn. Then, by clicking the OK button 102, the processing module creating unit 1 generates the source of the unload processing. The source generated by the processing module creation unit 1 is shown as a source 120 in FIG. In particular, the source generated by the unload processing is the screen erasing module 4. The screen erasing module 4 includes a screen transition number setting instruction 5 for setting the unload comparison value to FormReturn, and “Unload Me” (FIG. 2).
3 (A)). Based on the above procedure, unload processing is set for the "I like" button 61.

Next, the processing procedure for setting the confirmation message processing for the "I do not like" button on the screen 118 in FIG. 6 will be described below. First, the screen 118 is displayed, and the "I do not like" button is clicked. Then, the operation selection screen 90 to be added shown in FIG. 21 is displayed by the same procedure as the setting procedure of the unloading process. Then, since there is a confirmation message processing in the additional processing selection list box 91 of the operation selection screen 90 to be added, the user selects the processing and clicks an OK button 92. Then, the confirmation message processing setting screen 110 of FIG. 24 is displayed.
Set the processing details. First, a screen title is set in the title text box 111. The set title is the screen title displayed on the confirmation screen 80 in FIG. Also, the message content text box 112
, A message to be displayed on the confirmation screen 80 (the message on the confirmation screen 80 of FIG. 6 is “Is it true?”) Is set. Also, a type selection option group 116
Of the buttons to be displayed on the confirmation screen 80 are selected. The selected button type is button combo box 1
13 is displayed. The standard button of the type selection option group sets a default button on the confirmation screen 80. The default button referred to here is, for example, when the screen is switched to another screen without clicking any button on the confirmation screen 80 while the confirmation screen 80 is being displayed, the button is clicked before transitioning to another screen. It is a button to be done. The first button is selected as the standard button.
Thus, the default button is a "Yes" button (the "No" button is a second button). The button displayed in the button combo box 113 specifies a button to be notified of which button has been clicked on the confirmation screen 80. For example, “Yes” is selected in the button combo box 113 in FIG. In the confirmation message processing, if the "Yes" button is clicked,
Notifies that the "Yes" button has been clicked. The shape of the icon of the type selection option group is displayed on the confirmation screen 8
0 Specifies the shape of the icon to be displayed. Confirmation screen 80
Then, since the icon of "?" Is displayed, the inquiry is selected. After the setting is completed, when the OK button 114 is clicked to determine the processing content, the source of the confirmation message processing is generated by the processing module creating unit 1 in the pattern shown in FIG. The source of the confirmation message processing created by the processing module creating unit 1 is shown as a source 121 in FIG. As shown in FIG. 23 (B), the confirmation message processing is performed by using Msg in Visual Basic.
Box instruction is used. Therefore, the processing specification is Ms
It is based on the gBox specification. Therefore, the confirmation screen 80
The confirmation screen 80 is erased when any one of the “Yes” or “No” button is pressed. FIG.
In the setting of (B), “Is true?” Which is the message content set in the message content text box 112, the button type set in the button combo box 113, the icon shape of the type selection option group 116, and the (MsgBox specification) Then, when the "Yes" button and the "No" button are displayed and the inquiry message icon is displayed, the value becomes "36") and the title set in the title text box 111, "Confirm"
Set the instruction generated based on. This allows
An instruction "If MsgBox (" Is it true? ", 36," Confirmation ")" is generated. MsgBox returns a value indicating the pressed button. Since the value is predetermined according to the specification of MsgBox, it is used. Therefore, “If MsgBox〜 = Num” in FIG.
ber Then "determines the type of button pressed,
This is a command for determining whether or not to perform the processing after “Then”. In the confirmation screen 80 shown in FIG. 6, when the "Yes" button is clicked, the screen 1 is erased, and the processing ends. For this reason, when the "Yes" button on the confirmation screen 80 is clicked, an unload process for deleting the screen 1 is required. Therefore, the "I do not like" button is set to perform unload processing after confirmation message processing. When unload processing is set to be performed after the confirmation message processing, “If to Then” in FIG.
After the “FormReturn to Unl” in FIG.
“od Me” is subsequently inserted. The inserted source is shown as source 121 in FIG. When the “No” button on the confirmation screen 80 is clicked, the confirmation message processing ends, and the processing returns to the screen 1. Therefore, "If
“-Then” is an instruction to confirm whether the “Yes” button has been clicked, and “Number” has “6” indicating that the “Yes” button was selected as the standard button.
Is set. The setting of the unloading process is performed in the same procedure as the setting of the unloading process for the “I like” button 61. In the unload processing of the "I like" button 61, the unload comparison value set in the branch part parameter of FIG. 12 was set, but the unload comparison value of the "I do not like" button is other than "1". Take an integer value. This is because if "1" is set in the screen control module, the screen 2 is controlled to be displayed. Therefore, “3” is set as the unload comparison value in the unload processing of the “I do not like” button. "I don't like anything"
The button unload processing is performed by the source 121 shown in FIG.
ormReturn-Unload Me ". In the source 121, the If statement corresponds to the confirmation message processing, and the FormReturn and Unloa
The instruction d corresponds to the unload processing.

After the screen is changed to the screen 219,
Click the "Yes" button on screen 219 to display screen 2
Is erased, and the screen transitions to screen 118. For this reason,
Unload processing is also set on the “Yes” button on the screen 219. The source of the unload processing generated by the processing module creation unit 1 is shown as a source 122 in FIG. The source 123 in FIG. 25 is a source for the screen 2, and is a process of capturing the input value so that the input value for “name” input on the screen 1 is displayed on the screen 219. . Specifically, “Monkey” is input on screen 118 in FIG. 6, and “Monkey” is displayed on screen 219.
But to display it, the value "Monkey" is displayed on screen 21.
9 The value "Monkey" is Glob
stored in alData (1). In the source 123, the value stored in GlobalData (1) is Label2. Cap
stored in the. The process for the event on each screen is set by the above procedure.

Next, the flow of screen control by the execution unit 17 will be described. FIG. 26 is a flowchart showing the flow of screen control by the execution unit. In FIG. 26, execution unit 17 first displays screen 118. Then, it waits for an event to occur on the screen 118. Alternatively, it waits until the screen 118 is unloaded (S30). The event is triggered by entering a name on screen 118 or clicking a "I like this" button or a "Nothing I like" button. When an event occurs (S31), control is transferred to the process set for the button (S32). For example, when the “I like this” button is clicked (S33), the screen 118 is deleted (S34), and the screen 219 is displayed. Then, screen 2 is unloaded or screen 2 1
The process waits until the “Yes” button in 9 is clicked and an event occurs (S35). In the above S30 to S34,
Until the screen 118 is erased, the screen 118 has control. When the screen 118 is erased and the screen 219 is displayed, the control moves to the screen 219. When an event occurs on the screen 219 (S36), the screen 219 is deleted (S37), the screen 118 is displayed again, and the above-mentioned S3 is executed.
The processing from 0 is repeated. When “Nothing likes” is clicked on the screen 118, a message box as a confirmation screen 80 is displayed. Then, on the confirmation screen 80, a "Yes" button or
Wait until the "No" button is clicked (S3
8). At this time, the control remains on the screen 118. When an event occurs on the confirmation screen 80 (S
39), the message box as the confirmation screen 80 is deleted (S40). If the event in S39 has occurred due to the “Yes” button being clicked (S41), the screen 118 is deleted, and the process ends (S42). If the occurrence of the event in S39 is caused by clicking the “No” button on the confirmation screen 80, the screen 118 is displayed again, and the processing from S30 is repeated. Thus, the execution unit 17 performs the screen transition processing according to the screen transition module 13.

The screen transition control device of the present invention has a function of displaying a screen control flowchart created by the flowchart diagram creating / drawing unit 11 on a display device. The displayed image is similar to the flowchart shown in FIG. Further, the screen transition control device of the present invention has a function of printing a flowchart of screen transition. FIG. 27 is a diagram illustrating an example of printing a flowchart of screen transition. FIG.
Is similar to FIG. 9 except that the value of FormReturn for determining whether or not to unload the screen 1 is displayed at the branch process of “I like the button?” (FIG. 27). "Unload =
1? Is this).

As described above, the screen transition processing can be centrally managed by the screen transition module by using the screen transition control device of the present invention. Therefore, it is easy to grasp the entire screen transition process. In addition, the screen transition module can be constructed by the flowchart diagram creating / drawing unit using the flowchart components, and the instruction generating unit generates the source based on the created flowchart diagram, so that the user can visually generate the screen transition module. can do.

[0033]

According to the present invention, the screen transition control device comprises:
The configuration is as described above. For this reason, the following effects are obtained.

A screen transition module for controlling transition of a plurality of screens and a processing module used for data processing are separately managed. Therefore, there is an effect that the entire screen transition process can be managed in a unified manner. Further, in terms of maintainability, by centrally managing the screen transition processing, when the order of the screen transition processing is changed, a changed portion can be easily specified, and development costs and maintenance costs can be reduced. effective.

Further, the screen transition module can be visually created using a flowchart. Therefore, there is an effect that the entire flow of the screen transition process can be easily grasped.

The flowchart is composed of predetermined parts. Therefore, there is an effect that a user other than the creator of the screen transition module can easily grasp the flow of the screen processing by looking at the flowchart. Further, the created flowchart is automatically developed into an event-driven programming language. For this reason, the generated source is standardized,
There is an effect that debugging can be easily performed.

The processing for an event occurring on each screen is created and managed as a processing module separate from the screen transition module. Then, according to the screen control order of the screen transition module, the screen transition process is executed so as to call the process for the event on each screen while developing the screen transition process. For example, a process of deleting a predetermined screen when a certain event occurs is created separately from the screen transition module. As described above, since the screen transition module and the processing module can be completely separated and managed, there is an effect that maintainability can be improved.

The screen transition module and the erasure processing module have variables that can be referred to each other, and set a screen transition number as a criterion for selecting a screen to be displayed next in the above variables. For this reason, if a transition number that is unique for each screen is determined, the screen transition processing in one project is performed based on a unified value, and the maintainability of the project can be improved. There is.

Further, the source of the processing module is automatically generated according to a predetermined pattern. For this reason, the source of the created processing module is standardized without any individual differences among users who created the processing module. Therefore, there is an effect that debugging can be easily performed and maintainability can be improved.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of a screen transition control device according to the present invention.

FIG. 2 is a diagram showing a screen displayed when a flowchart diagram creation drawing unit is started.

FIG. 3 is a diagram showing processing contents of each of the flowchart component groups in FIG. 2;

FIG. 4 is a diagram showing sources developed from the flowchart component group of FIG. 2;

FIG. 5 is a flowchart showing a processing procedure performed by a user to use the screen transition control device according to the present invention.

FIG. 6 is a screen transition diagram showing a screen transition according to the first embodiment.

FIG. 7 is a diagram in which a flowchart diagram drawing unit according to the first embodiment is selected from a menu.

FIG. 8 is a diagram showing a screen for creating a screen transition flowchart according to the first embodiment.

FIG. 9 is a diagram showing a flowchart created based on the screen transition shown in FIG. 6;

FIG. 10 is a diagram illustrating setting of parameters of a screen display component.

11 is a diagram showing a list box of a form name in FIG.

FIG. 12 is a diagram showing a parameter setting screen of a branch part.

FIG. 13 is a diagram showing a branch style in FIG. 12 using a flowchart.

FIG. 14 is a diagram for setting parameters of a jump component.

FIG. 15 is a view showing a pull-down menu of a file shown in FIG. 8;

FIG. 16 is a diagram showing the source of the screen transition module developed from the flowchart of FIG. 9 in the first embodiment.

FIG. 17 is a diagram illustrating a setting procedure of an unloading process by the processing module creating unit according to the first embodiment.

FIG. 18A is a diagram showing a part of the form of the screen 1 in FIG. (B) is a diagram showing an example of a pull-down menu displayed by selecting an add-in of the main menu in the first embodiment.

FIG. 19 is a diagram showing an event selection screen according to the first embodiment.

FIG. 20 is a diagram showing an operation content setting screen according to the first embodiment.

FIG. 21 is a diagram showing an operation selection screen to be added in the first embodiment.

FIG. 22 is a diagram illustrating an unload processing setting screen according to the first embodiment;

FIG. 23A is a diagram showing a source source of an unload process. (B) is a figure which shows the generation source of confirmation message processing.

FIG. 24 is a diagram showing a confirmation message processing setting screen.

FIG. 25 is a diagram showing a source of processing for an event on each screen.

FIG. 26 is a flowchart showing a procedure of processing in an execution unit.

FIG. 27 is a diagram illustrating an image when a flowchart of a screen transition process is printed and displayed on a screen.

FIG. 28 is a diagram showing setting of screen transition processing in a conventional example.

[Explanation of symbols]

1 processing module creation unit, 2 processing modules A, 3
Processing module B, 4 screen erase module, 5 screen transition number setting instruction, 6 erase instruction, 7 screen creation unit,
8 screen 1, 8a button 1, 9 screen 2, 10 screen transition module creation unit, 11 flowchart diagram creation drawing unit, 12 instruction generation unit, 13 screen transition module,
14 screen 1 display instruction, 15 screen transition number judgment processing,
16 screen 2 display instruction, 17 execution unit, 18 screen 1,
19 Screen 2, 20 Work area, 21 Flowchart parts group, 22 Arrow, 23 Start terminal, 24 Screen display part, 25 Branch part, 26 Jump part, 27 End terminal, 28 Connection line, 29 File menu, 30
Main window, 31 parts window, 32 work area, 40 setting menu, 41 display part parameter setting screen, 42 form name text box, 43 Japanese name text box, 44 setting button, 45 cancel button, 50 branch parameter setting screen, 51
Branch style, 52 unload comparison value combo box, 53 Japanese name text box, 54 setting button, 55 cancel button, 56 jump part parameter setting screen, 57 part name text box,
58 setting button, 59 cancel button, 60 screen setting screen, 61 "I like" button, 62 main menu, 63 pull-down menu, 64 processing module creation, 70 event selection screen, 71 event display list box, 72 selection button, 73 cancel Button, 80 confirmation screen, 81 continuous processing contents list box, 82 add button, 83 edit button, 84
Delete button, 85 OK button, 86 cancel button, 87 operation content setting screen, 90 operation selection screen to add, 91 additional processing selection list box, 92 OK
Button, 93 cancel button, 100 unload processing setting screen, 101 unload comparison value combo box, 102 OK button, 103 cancel button,
110 confirmation message processing setting screen, 111 title text box, 112 message content text box, 113 button combo box, 114 O
K button, 115 cancel button, 116 type selection options, 120-123 sources.

──────────────────────────────────────────────────続 き Continued on the front page (58) Field surveyed (Int.Cl. ⁷ , DB name) G06F 9/06 G06F 9/44

Claims (5)

(57) [Claims] [Claim 1] with (a) event-driven programming method, screen creation section that creates a processing module creation unit for creating a processing module used for data processing, a plurality of screens to be used in (b) said data processing When the screen transition module creating unit that creates a screen transition module for controlling transitions of the (c) said plurality of screens, to control the transition of the plurality of screens based in (d) of the screen transition modules, the processing Screen transition control with an execution unit that executes data processing using a module
Device, wherein the screen transition module creation unit indicates the start of processing.
Parts, and parts that indicate screen display,
Parts that mean branching of processing by
And the end of processing
Having the above five flowchart parts,
Combine the necessary parts among the flowchart parts
Flow chart of screen transition that visually represents surface transition processing
A flowchart drawing and drawing section for drawing and drawing a screen ,
Command generator that generates screen transition control commands corresponding to
A screen transition control device, comprising: 2. The screen transition control device according to claim 1, wherein the screen transition module creation unit automatically creates the screen transition module from a flowchart. 3. The processing module creation unit according to claim 1 , wherein
A screen to delete the displayed screen as one of the modules
An erasing module is created.
Is a screen transition control device according to 2. 4. The screen erase module according to claim 1 , wherein
Erase command to erase and select the next screen to display
Output the screen transition number to the above screen transition module
A screen transition number setting instruction;
Enter the screen transition number and enter the screen transition number
That then selecting and displaying a screen to be displayed on the basis
The screen transition control device according to claim 3, wherein: 5. The processing module creating unit according to claim 1 , wherein
Command and the screen transition number setting command
5. The screen transition control device according to claim 4, wherein