JP4045468B2 - Graphical user interface controller - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a graphical user interface (hereinafter referred to as GUI) in an operating device of various devices such as air conditioning, lighting, power distribution, and home appliances.
[0002]
[Prior art]
In recent years, for the purpose of improving the operability of low-cost operating devices such as operating equipment for building equipment systems and operating equipment for consumer equipment that control the operation of various equipment such as air conditioning and lighting of buildings, for example, on personal computers or workstations The movement to introduce the mainstream GUI operation method is becoming active. However, in general, an operation device using a GUI operation method needs to handle a large amount of data such as display image data and sound data representing a response, which are various components of the operation device screen such as a window, a button, and an icon. A large amount of memory and a high performance CPU are required. This raises the cost of the operating device, which is an impediment to the penetration of the operating device by the GUI operation method.
[0003]
Recently, in an operation device in a GUI operation method, a GUI is often implemented using object-oriented technology for the purpose of improving software productivity by reuse. In general, GUI is implemented by controlling screen display, The display image data and the information of the device connected to the operation device are configured as an integrated object, or further configured as an object to which the operation procedure is added. An object refers to data or a program in which data and operations on the data are integrated.
[0004]
  As an example of a GUI using such an object-oriented technology, there is an invention disclosed in JP-A-6-202863.
[0005]
The GUI application program design support system disclosed in this publication includes a first event setting object for setting display switching of each window on the screen, a simulated environment setting object for creating a simulated window, and the operation contents for the window and each Independent object such as procedure setting object that performs window operation and continuous procedure setting is implemented as a collection, and prototyping of overall operation of GUI can be done in detail and flexibly, making application program design efficient It is to support.
[0006]
[Problems to be solved by the invention]
The conventional GUI application program design support system as described above also requires a large amount of memory and a high-performance CPU because a large amount of image data and sound data need to be managed and processed.
[0007]
As a result, the cost of the operation device is raised, and the penetration of the operation device by the GUI operation method into various device fields where low cost is required is hindered.
[0008]
The present invention has been made in order to solve the above-described problems, and improves the use efficiency of the memory by sharing the data used redundantly and the data expansion process, and also provides the invariant attribute data of the object. It is intended to provide a graphical user interface that can be stored in inexpensive hardware and can be implemented at low cost.
[0009]
[Means for Solving the Problems]
  The graphical user interface operating device according to the present invention has a plurality of screen objects composed of a slide object and an icon object corresponding to each display screen, and controls screen display based on the screen object specified from the plurality of screen objects. Various data including display objects for detecting user operations and operation information and setting information of the devices and systems to be controlled by the display objects are separated from the display objects and managed based on the operation information on the display screen. Has a database object and a screen transition management table based on each operation, inputs the operation detected in the display object, and corresponds to the next display screen to be displayed based on the screen transition management table based on that operation A procedure object that identifies the screen object Once the operation information detected by the display object is received, it is transmitted to the database object, and after receiving the data corresponding to the operation information output from the database object, the screen object of the display object specified by the procedure object Link object that transmits to the screen object via the slide object and displays the screen corresponding to the operation on the screen object.Of the attribute data of each object consisting of a variable part whose data contents are changed by operation and an invariant part which is not changed, the variable part is stored in the RAM and the invariant part is stored in the ROM.
[0011]
  Also, a graphical user interface according to the present inventionControllerThe operation is predicted after the data object consisting of multiple objects that separate the physical data used in the screen object of the display object from the display object and the screen object that generates the display screen. When one or more screen objects to be specified are specified by the procedure object, a corresponding screen object is extracted in advance based on the specification, and an object corresponding to the corresponding screen object is previously extracted from the data objects Management objects.
[0012]
  Furthermore, the graphical user interface according to the present inventionControllerThe memory management object generates one or more display screen data in advance based on the further extracted screen object and data object.
[0013]
  Also, a graphical user interface according to the present inventionControllerThe procedure object calculates the transition probability of the display screen for the operation detected in the display object, and designates one or a plurality of screen objects whose operations are predicted next as memory management objects based on the transition probability. Is.
[0014]
  Graphical user interface according to the present inventionControllerHas a decompression object that decompresses a pre-compressed data object as needed.
[0015]
  Also, a graphical user interface according to the present inventionControllerHas a decompression object that decompresses a data object corresponding to the image object out of the pre-compressed data objects when the screen object is specified by the procedure object.
[0016]
  Graphical user interface according to the present inventionControllerThe link object is a forward link object that links the display object and the database object and transmits the data of the display object to the database object, and a reverse direction that links the display object and the database object and transmits the data of the database object to the display object. A link object.
[0017]
  Also, a graphical user interface according to the present inventionControllerHas an object management table that manages the correspondence between the object name and the address where each object exists, intervenes between the objects when sending a message, and identifies the address of the destination object based on the object management table It has a message exchange service object that forwards messages to the object at that address.
[0018]
  Furthermore, the graphical user interface according to the present inventionControllerIs composed of a fixed-length message composed of a communication destination object name, a service number to be used, and a pointer address to a parameter exchanged between objects.
[0020]
DETAILED DESCRIPTION OF THE INVENTION
FIG. 1 is a configuration diagram of first to tenth embodiments of the present invention. In this embodiment, for example, an operating device for a building equipment management system that monitors and operates air conditioning, lighting, and the like installed in a building will be described as a specific example.
[0021]
In the figure, reference numeral 100 denotes a graphical user interface (GUI) implemented in the operating device 200 for a building facility equipment management system, and is composed of a plurality of objects to be described later. Reference numeral 1 denotes a display object having functions for controlling display of the GUI 100 and detecting a user's operation, 2 is a data object which is physical data such as image data and audio data used in the display object 1, and 3 is a monitor / monitor Database with configuration information related to the building equipment management system to be operated, various data including operation information and setting information of equipment (for example, indoor units, lighting equipment, etc.), and a function for managing the database Object 4 is a link object having a function of linking display object 1 and database object 3 and exchanging data of both objects 1 and 3, and 5 is a transition procedure between display operation screens of operation device 200, that is, each screen A procedure object with an operation procedure management function corresponding to the operation of Extract, 6 is a network managed object having a management function for communication with the operating device 200 and building equipment management system.
[0022]
Reference numeral 101 denotes a GUI 100 mounted on the operation device 200 and a multi-task real-time operating system (hereinafter referred to as a real-time OS) such as μITRON for managing execution of various applications, and 102 denotes a display driver and an audio driver for operating hardware. A driver (software) group 103 includes hardware such as a microcomputer, a ROM, a RAM, and a display element (LCD) constituting the operation device 200. Each object 1, 2, 3, 4, 5, 6 operates functionally independently by the management function of the real-time OS 101, and realizes the function of the entire GUI by mutual message exchange. In addition, the display object 1, the data object 2, and the database object 3 are usually composed of a plurality of objects.
[0023]
Embodiment 1. FIG.
FIG. 2 is a diagram illustrating the configuration of the main part of the first embodiment of the present invention. In the figure, reference numeral 10a denotes a push button of, for example, “1F common area illumination” displayed on the display operation screen on the operation device 200, and the 1F illumination of the display object 1 having the display control function and the user operation detection function. When receiving an operation from the image object 21 of the data object 2 and the user used in the icon object 11a and its 1F lighting icon object 11a (display object 1) and actually displayed on the display operation screen, and the operation device 200 And the sound data object 22 of the data object 2 originating from the. 31a, 31b,... Are, for example, the lighting 1 object and the lighting 2 object of the database object 3 corresponding to the target device, group or system monitored / operated by the operating device 200, and their operating states (current value = [ON | OFF]). ), Information on button positions and sizes of the display operation screen, and the like are stored. 41a, 41b, etc. are, for example, a 1F lighting object and a 2F lighting object of the link object 4, and the 1F lighting object 41a associates the 1F lighting icon object 11a of the display object 1 with the lighting 1 object 31a of the database object 3, and the 1F lighting icon object The operation information of the user 11a is transmitted to the lighting 1 object 31a to rewrite the contents of the lighting 1 object 31a.
[0024]
1F lighting icon object 11a (display object 1), image data object 21 and sound data object 22 (data object 2), lighting 1 object 31a and lighting 2 object 31b (database object 3), and 1F lighting object 41a A GUI 100 mounted on the operation device 200 as shown in FIG. 1 is configured by a plurality of objects such as the 2F lighting object 41b (link object 4).
[0025]
As described above, since each object operates functionally independently, each object can be freely designed, and the burden on the designer can be reduced. In addition, for example, even when a change occurs in the display operation screen of the operation device 200, the database portion may not be changed if the basic configuration of the GUI 100 does not change.
[0026]
A GUI object designed and implemented in a conventional object-oriented manner is a form in which various data corresponding to the object are attached to each object, for example, a display control part and display data are integrated. It was. Therefore, in the GUI 100 according to the first embodiment of the present invention, as shown in FIG. 3, among various data of each object of the GUI 100, for example, the push button 10 a displayed on the display operation screen on the operation device 200. , 10b... And the unique data such as the display position and size of the display object 1 are directly held by the 1F lighting icon object 11a, the 2F lighting icon object 11b, the 3F lighting icon object 11c, etc. of the display object 1, and the push buttons 10a, 10b. Physical data that can be shared, such as basic image data such as images and icons, sound data used for operation sounds, and the like are the image data object 21 and the sound data object 22 of the data object 2. And it is configured to have made independent from the display object 1 in etc..
[0027]
In this way, physical data that can be shared is provided in the data object 2 that is separated and independent from the display object 1 and is shared by a plurality of objects of the display object 1, so that the image data and sound that are likely to become large as data can be obtained. Duplication of physical data such as data can be prevented, and waste of expensive memory can be avoided.
[0028]
Further, in the GUI 100 according to the first embodiment of the present invention, as shown in FIG. 2, operation information and settings of devices and systems to be controlled by the display object 1 associated with the display object 1 or the like conventionally. Various data including information are provided in a database object 3 that is separated and independent from the display object 1 so as to operate functionally independently. Therefore, the data transmission from the display object 1 to the database object 3 is not performed directly by the both 1, 3, but via the link object 4. Thereby, independence of the display object 1 and the database object 3 can be improved more.
[0029]
For example, as shown in FIG. 4, when the push button 10e of one of the push buttons on the display operation screen “large meeting room lighting” has a group control function for collectively operating a plurality of illuminators, The large conference room lighting icon object 13 of the display object 1 corresponding to the “illumination” push button 10e, the illuminator 1 object 31a of the database object 3 corresponding to the plurality of illuminators subject to group control, and the illuminator 2 The objects 31b are linked via the large meeting room lighting group object 43 of the link object 4. Thus, the large meeting room lighting icon object 11e (display object 1) only needs to give an instruction to the large meeting room lighting group object 43 (link object 4). It is not necessary for the container 1 object 31a and the like (database object 3) to know the contents of the other. Therefore, when the number of illuminators in the large conference room is changed, it is only necessary to change the attribute data related to the database object 3 managed by the large conference room lighting group object 43 (link object 4). There is no need to make changes to the display object 1 and the database object 3.
[0030]
As described above, in the GUI 100 according to the first embodiment of the present invention, the display object 1 and the database object 3 are directly related, and the display object 1 needs to directly issue instructions to a plurality of objects of the database object 3. In addition, there is no need to change many attribute data of the display object 1 even when the contents of the group control are changed. Thereby, each object can ensure sufficient independence.
[0031]
Further, even when a plurality of controls are performed on the same content, for example, when the time display is performed in two ways of digital display and analog display, as shown in FIG. The link between the clock object 32 for managing the actual clock data of the database object 3 and the digital clock object 15 of the display object 1 and the link between the clock object 32 of the database object 3 and the analog clock object 16 of the display object 1 When the user selects (operates) either the digital clock button 10g or the analog clock button 10h, the clock link object 45 of the link object 4 stores the data of the selected object. Transmitted to the clock object 32 of transfected 3 displays a digital or analog. As described above, since the display object 1 and the database object 3 do not need to know the contents of the other one as in the case of group control, each object can ensure sufficient independence.
[0032]
As the link object 4, as shown in FIG. 2, the 1F illumination of the link object 4 corresponds to the 1F illumination icon object 11a of the display object 1 and the illumination 1 object 31a of the database object 3 corresponding one-to-one. When one of the objects 41a corresponds, and as shown in FIG. 4, one object of the link object 4 corresponds to one object of the display object 1 and a plurality of objects of the database object 3 corresponding to one to a plurality. And a case where one of the link objects 4 corresponds to a case where a plurality of objects of the display object 1 correspond to a plurality of objects of the database object 3 as shown in FIG. and so on. Further, as shown in FIGS. 6 and 7, the one-to-one link, the one-to-multiple link, or the plurality of one-to-one links described above are one link object 46a, 46b itself and the property of the link object 46a, 46b. In some cases, the display object 1 is linked to the database object 3 by linking the display object 1.
[0033]
Embodiment 2. FIG.
FIG. 8 is a diagram illustrating the configuration of the main part of the second embodiment of the present invention. In the figure, 17 corresponds to one object 17a, 17b,... For each screen displayed on the operation unit, and is a slide object for managing all push buttons and the like existing on the screen. Is composed of an icon object 18 (icon objects 18a, 18b...) For controlling the image object and a data object 24 (data objects 24a, 24b...) Having image data and sound data used in the icon object 18. A display operation screen is generated by a plurality of screen objects (display object 1) made up of icon objects 18. The slide object 17 and the icon object 18 (screen object) are held in the display object 1, and the data object 24 is held in the data object 2. Reference numeral 33 denotes a database object corresponding to each icon object 18, such as a target device (for example, an illuminator) monitored or operated by an operating device, a group or system operating state, a push button display position and size on the screen, and the like. The database objects 33a, 33b... And the icon objects 18a, 18b... Are linked by link objects 47a, 47b. Further, the database object 33 is held in the database object 3, and the link objects 47 a, 47 b... Are held in the link object 4.
[0034]
A function 5 identifies a slide object 17 (screen object) corresponding to a display operation screen required in accordance with a user operation, and manages a transition procedure between display operation screens, that is, an operation procedure corresponding to an operation on each screen. .., Each of the slide objects 17a, 17b..., That is, a screen transition management table 51a, 51b... For each screen, and the icon object 18 on each display operation screen (each slide object 17) and its icon. The table manages the correspondence with the display operation screen (slide object 17) of the next transition destination when a push button or the like corresponding to the object 18 is operated.
[0035]
For example, when the display operation screen A corresponding to the slide object 17a is currently displayed on the operating device, buttons A-1 to A-6 corresponding to the icon objects 18a. When the user operates the button A-1, as shown in FIG. 8, the icon object 18a detects the operation and transmits the operation information to the database object 33a via the link object 47a. At the same time, the operation information is transmitted to the procedure object 5 via the slide object 17a. The procedure object 5 refers to the screen transition management table 51a of the slide object 17a, and the button A-1 corresponding to the icon object 18a is operated. The transition screen and the slide object 17b are specified, and an instruction to display the display operation screen B corresponding to the slide object 17b is issued on the operating device. Then, the display operation screen B is displayed as the next screen on the operation device.
[0036]
Here, it is assumed that the button A-1 corresponding to the icon object 18a is a “device 1” button for operating the device 1. As shown in FIG. 9, when the user operates the “device 1” button 10j on the display operation screen A displayed on the operation device 200, the icon object 18a indicates that the “device 1” button 10j is operated. Detecting and transmitting the operation information, that is, “information indicating that the device is 1” to the procedure object 5 through the slide object 17a, and the procedure object 5 is a slide corresponding to the next screen by the screen transition management table 51a of the slide object 17a. The object 17b is specified, and the operation information “information indicating that the device is 1” is transmitted to the slide object 17b. The slide object 17b includes a screen template 300 for composing the screen. By adding operation information to the template 300, the same information is transmitted to the icon object 19a constituting the display operation screen B and the like. The object 19a and the like transmit the same information to the link object 48a and the database object 33 and the like. The slide object 17b constitutes a display operation screen B with operation buttons 10k, 10m, etc. corresponding to the icon object 19a. A display operation screen B is displayed on the operation device.
[0037]
That is, as shown in FIG. 9, the operation information on the display operation screen A is transmitted to the slide object 17b corresponding to the next screen via the procedure object 5, and the operation information is added to the template 300 included in the slide object 17b. Thus, the slide object 17b can issue a display instruction to the icon object 19a and the like constituting the display operation screen B to be displayed corresponding to the operation. The icon object 19a and the like correspond to the database object 33 through the link object 48a and the like, and the “object 1” button 10j operated by the slide object 17b, the icon object 19a, the link object 48a and the database object 33 is displayed. A display operation screen B corresponding to the actual device 1 is configured.
[0038]
In this way, by managing the transition of the next screen by the procedure object 5, even when the transition procedure or the like is changed, only the procedure object 5 needs to be changed without changing other objects such as the slide object 17. Therefore, changes and modifications can be easily performed. Further, the slide object 17 only needs to manage the use of operation buttons and the like on the screen, and the display operation screen to be displayed can be easily configured by the screen template 300 and the operation information of the display object 1. Therefore, when similar monitoring / operation is performed on each device to be controlled, the same display operation is performed on each of the operation buttons 10j, 10n, and 10p displayed on the display operation screen A as shown in FIG. Duplicate screens B, C, D... Can be avoided, and the amount of memory used can be saved. Also, when there are multiple targets such as group control or schedule setting, there are many functions that are operated in the same procedure, so the procedure itself can be shared and prepared as a template to be reused in the development of other operating devices. Design efficiency can be improved.
[0039]
Embodiment 3. FIG.
FIG. 10 is an explanatory diagram of the configuration of the main part of the third embodiment of the present invention. This embodiment is the next to the display operation screen displayed on the operating device by the procedure object 5 in the second embodiment. The slide object 17 corresponding to the display operation screen that is predicted to be displayed, the icon object 18 and the data object 24 corresponding thereto are extracted, and the display predicted based on the extracted slide object 17, icon object 18, and data object 24 is extracted. It has a memory management object 7 for generating display operation screen data of the operation screen in advance and temporarily storing the generated display operation screen data in the memory block 7a.
[0040]
In this embodiment configured as described above, it corresponds to a display operation screen that is predicted to be displayed next to the display operation screen displayed on the controller based on the operation procedure managed by the procedure object 5. The procedure object 5 specifies a plurality of slide objects 17 and instructs the memory management object 7 to generate a display operation screen entity corresponding to the specified slide object 17. Next, the memory management object 7 that has received the instruction works on the real-time OS 101 to secure the memory capacity as much as possible out of the memory capacity necessary for generating the actual display operation screen of the memory mounted on the controller. A memory block 7a is prepared. At this time, if not all the required memory capacity can be secured, a capacity that can be secured for each screen is secured. Then, the memory management object 7 extracts the slide object 17 specified by the procedure object 5 and the icon object 18 and data object 24 corresponding to the slide object 17 and generates display operation screen data based on the extracted objects 17, 18, 24. And stored in the memory block 7a. That is, when the display operation screen A corresponding to the slide object 17a is displayed on the operation device, the procedure object 5 displays the slide objects 17b and 17d corresponding to the display operation screens B and D that will be displayed next. Specifically, the memory management object 7 is instructed to generate the entity, and the memory management object 7 generates the display operation screens B and D data based on the slide objects 17b and 17d and the like, as shown in FIG. The display operation screens B and D data are stored in the memory block 7a.
[0041]
As described above, the procedure object 5 specifies the slide object 17 or the like corresponding to the display operation screen predicted to be displayed next based on the operation procedure of the procedure object 5, and the memory is determined based on the specified slide object 17 or the like. Since the management object 7 generates the display operation screen data and stores it in the memory block 7a in advance, the generation operation of the display operation screen below the slide object 17 of the screen to be displayed next after receiving the instruction of the procedure object 5 is performed. Therefore, it is not necessary to perform the operation every time the display operation screen is operated, and the time for screen generation work can be shortened. Thereby, the response of the operating device can be improved and the operability can be improved.
[0042]
Embodiment 4 FIG.
In the fourth embodiment, the slide object 17 corresponding to the display operation screen predicted to be displayed next is specified based on the operation procedure managed by the procedure object 5 in the third embodiment. Instead, it is performed based on the transition probability calculated based on the operation frequency of the user, and the number of times that the user has operated each of the icon objects 18 and the display operation screen transitioned by the operation are displayed on the procedure object 5. Is provided with a transition probability calculating means for calculating an operation frequency based on the number of operations in the slide object 17 corresponding to the above and calculating the transition probability by summing up the operation frequencies for each slide object 17. As shown in FIG. 11A, the procedure object 5 has a screen transition management table 51 (51a...) Provided with an operation frequency column for each icon object 18, and also shown in FIG. 11B. As described above, the transition probability management table 52 (52a...) Corresponding to the transition probability in each transition object slide object 17 is provided.
[0043]
Then, the procedure object 5 specifies, for example, the slide objects 17b and 17d having the highest transition probability based on the transition probability management table 52 as the slide object 17 corresponding to the display operation screen predicted to be displayed next. Then, before the operation is actually performed, the memory management object 7 is instructed to generate the entities of the display operation screens B and D. Then, as shown in FIG. 10, the memory management object 7 stores the generated display operation screens B and D data in the memory block 7a.
[0044]
As described above, the display operation screen data generated by the slide object 17 or the like having a high transition probability can be stored in the memory block 7a in advance before the operation based on the transition probability management table 52 of the procedure object 5, so that the user It is possible to increase the screen transition speed adapted to the operation tendency, and to improve the response of the operating device and the operability.
[0045]
Embodiment 5. FIG.
FIG. 12 is a diagram illustrating the configuration of the main part of the fifth embodiment of the present invention. In this embodiment, in the second embodiment, the data object 24 (24a, 24b...) Is stored in the ROM of the hardware 103 as the data object 25 (25a, 25b. The expansion object 8 that expands the data object 25 is provided when necessary.
[0046]
In this embodiment configured as described above, the procedure object 5 corresponds to the display operation screen to be displayed next based on the operation procedure managed by the procedure object 5 as in the case described in the second embodiment. For example, when the slide object 17a is specified, the icon object 18a corresponding to the specified slide object 17a specifies the data object 24a required for the decompression object 8. The decompression object 8 extracts the compressed data object 25a ... corresponding to the designated data object 24a ... from the data object group compressed and stored in the ROM, and performs decompression processing to generate the actual data object 24a ... Let The slide object 17a constitutes a display operation screen with the icon objects 18a, etc. using the generated data objects 24a, etc.
[0047]
In this way, the actual data objects 24a... Are compressed and stored in the ROM, and taken out by the decompression object 8 when necessary and decompressed. Therefore, the required memory capacity of the entire data object can be reduced and expensive. Can reduce the amount of memory used.
[0048]
Embodiment 6. FIG.
In the sixth embodiment, the invention in the fifth embodiment is implemented in the third embodiment, and a plurality of display operation screens that are predicted to be displayed next based on the operation procedure managed by the procedure object 5 are displayed. When the display operation screen data generated by the corresponding slide object 17 or the like is generated by the memory management object 7, the compressed data object 25 corresponding to the slide object 17 corresponding to a plurality of predicted display operation screens is displayed. A data object 24 is expanded by the expansion object 8 and a plurality of display operation screen data is generated by the data object 24 or the like.
[0049]
With this configuration, substantially the same effect as in the third and fifth embodiments can be obtained, and the memory used can be saved and the screen transition speed can be increased. Thereby, the response of the operating device can be improved and the operability can be improved.
[0050]
Embodiment 7. FIG.
In the seventh embodiment, the invention in the fifth embodiment is applied to the fourth embodiment, and a slide object corresponding to a display operation screen having a high transition probability based on the transition probability management table 52 of the procedure object 5 When the display operation screen data generated by 17 or the like is generated by the memory management object 7, the compressed data object 25 corresponding to the slide object 17 corresponding to the display operation screen having a high transition probability is expanded by the expansion object 8. The data object 24 is processed, and the display operation screen data having a high transition probability is generated by the data object 24 or the like.
[0051]
By configuring in this way, substantially the same effect as in the fourth and fifth embodiments can be obtained, and the screen transition speed adapted to the user's operation tendency can be increased by saving the memory used. Thereby, the response of the operating device can be improved and the operability can be improved.
[0052]
Embodiment 8. FIG.
FIG. 13 is an explanatory diagram of the configuration of the main part of the eighth embodiment of the present invention. This embodiment relates the display object 1 and the database object 3 in the first embodiment, and stores the data from the database object 3. A reverse object 49 of the reverse link object 4a that is transmitted to the display object 1 to rewrite the data of the display object 1 is provided.
[0053]
In this embodiment configured as described above, for example, when the user turns off the lighting 1 that is turned on, the light-off information is written to the lighting 1 object 31a of the database object 3, and the lighting 1 object 31a is the reverse link object 4a. The turn-off information is transmitted to the 1F illumination icon object 11a via the reverse object 49. Next, the 1F lighting icon object 11a takes out the data indicating the lighting off state from the lighting image data object 21 of the data object 2 based on this lighting off information, and the lighting 1 which is the lighting off state on the display operation screen on the operation unit. The push button 10a corresponding to is displayed.
[0054]
At this time, as shown in FIG. 14, the reverse lookup object 49 is based on the reverse link management table 400 provided in the reverse lookup object 49, from the key “illumination 1” of the illumination 1 object 31a. The key of the 1F lighting icon is extracted, and the information link to the 1F lighting icon object 11a is configured.
[0055]
The reverse link management table 400 is created as follows. First, as shown in FIG. 14, the link object (forward link object) 4 includes a display object 1 and a database that use the display object 1 side as a key based on the 1F illumination object 41a, the 2F illumination object 41b, and the like of the link object 4. A link management table 401 that is a correspondence table with the object 3 is created. Next, the display object 1 side and the database object 3 side are switched based on the link management table 401, and the reverse link management table 400 with the key as the database object 3 side is created and given to the reverse lookup object 49.
[0056]
Thus, by providing the reverse link object 4a separately from the link object (forward link object) 4, the data from the database object 3 can be transmitted to the display object 1 via the reverse link object 4a. The display object 1 can use the transmitted data. As a result, the display object 1 and the database object 3 can easily exchange data between the display object 1 and the database object 3 by the link object (forward link object) 4 and the reverse link object 4a, thereby expanding the data usage range. be able to.
[0057]
When a plurality of objects of the display object 1 correspond to one object of the database object 3, there are a plurality of the same keys on the database object 3 side which is a key of the reverse link management table 400, The data of the database object 3 is sent to the plurality of objects of the display object 1 corresponding to the key via the reverse lookup object 48 of the reverse link object 4a.
[0058]
Embodiment 9. FIG.
FIG. 15 is an explanatory diagram of the configuration of the main part of the ninth embodiment of the present invention, and FIG. 16A is a configuration diagram of messages communicated between objects. In this embodiment, in the third embodiment, a message exchange service object 9 having an object management table 9a whose contents are changed by the memory management object 7 of the third embodiment is provided, and each object of the display object 1 is provided. A service definition table 500 for managing service information defined for each (slide object 17 or the like) is provided to implement message communication between objects. Reference numeral 104 denotes a memory area provided by the real-time OS 103. Reference numeral 600 denotes a fixed-length message communicated between objects. As shown in FIG. 16A, a communication partner object name 601, a service number 602, and pointers to parameters. 603. The object management table 9a includes a correspondence table of object names and addresses where each object exists, and the service definition table 500 includes a correspondence table of service numbers and service names.
[0059]
In this embodiment configured as described above, for example, when a display request for the icon A-1 corresponding to the icon object 18a is generated from the slide object 17a to the icon object 18a, the slide object 17a should be transferred to the icon object 18a. The parameter is stored at a predetermined address (05010H) in the memory area 104, and is called “icon object (A-1) + service number 2 + parameter pointer (05010H)” according to the structure of the message 600 shown in FIG. The message 600 is created based on the service definition table 500 managed by itself, and transmitted to the message exchange service object 9. The message exchange service object 9 refers to the icon object (A-1) of the object name 601 from the transmitted message 600, that is, the icon A-1 memory from the object management table 9a managed by itself referring to the icon A-1. The upper address is specified, and the message 600 is transferred to the specified address, that is, the icon object 18a. Then, the icon object 18a extracts the service number 602 and parameter pointer 603 from the received message 600, interprets the service of “icon display” based on the service definition table 500 managed by the icon object 18a, and stores in the memory area 104. The parameter for the service stored at the address (05010H) is extracted from the address (05010H) in the message 600, and the “icon display” service is executed. Thereby, the icon A-1 is displayed on the display operation screen on the controller.
[0060]
In this way, the contents of the message 600 such as service type and parameters are defined in each object in which message communication is performed, and the message exchange service object 9 basically does not convert the message 600 based on the object management table 9a without any conversion. Since message transfer is realized, each object can be made functionally independent without managing the address of the other party to which the message 600 is transmitted, and can save memory and free up memory allocation. A GUI capable of realizing high message communication can be obtained. Further, when the memory arrangement of an object is changed by memory rearrangement or the like, the object management table 9a of the message exchange service object 9 need only be changed by, for example, the memory management object 7, so that the GUI design efficiency can be improved. it can. Further, since the message 600 to be communicated has a fixed length, the message communication process can be easily performed, and the function of the entire GUI can be enhanced.
[0061]
In the above-described embodiment, the message communication between objects is realized by the object management table 9a which is the all object batch table of the message exchange service object 9. However, for example, when the number of objects increases. As shown in FIG. 17, an object management table 9a of the message exchange service object 9 may be created for each category to perform message communication. In this case, the message 600 to be communicated is configured as shown in FIG. 16B, and an increase in search and management processing in the message exchange service object 9 can be avoided.
[0062]
Embodiment 10 FIG.
In the tenth embodiment, the attribute data and method of each object 1, 2, 3,... Are divided into a variable part and an invariant part based on the contents thereof. The portion is stored in the ROM of the memory.
[0063]
In order to apply the GUI over a wide range, cost reduction is important. For this reason, it is effective that the object is mounted on the operation device or the like based on a ROM base having a lower cost than the RAM. Therefore, in the attribute data and methods of the elements constituting each object 1, 2, 3,..., Methods that are not normally changed at the time of execution are stored in the ROM, and variable parts that may be changed at the time of execution are compiled. By storing the attribute data in which invariant parts that are not changed once determined at times are stored in the ROM and the RAM, the amount of RAM used can be significantly reduced.
[0064]
Next, a method for realizing ROM or RAM storage for each attribute data of the objects 1, 2, 3,... Will be described with reference to FIG. First, the designer analyzes whether each attribute data is likely to be changed at the time of execution or whether it is not changed later once it is determined. That is, the ID of the display image data of the data object 2 is not changed at the time of execution because the image data itself that becomes the base of the button is inserted, for example, and even when the process of deforming the image at the time of execution is possible Since a certain kind of operation is performed on the image data, the ID indicating the original image data is unchanged. On the other hand, the coordinate position data of the display object 1 is variable because the coordinate position changes at the time of execution, such as in the case of an operating device that enables the movement of the buttons displayed on the display operation screen. Such an analysis is performed on all the attribute data, and “ROM” is added to the invariant attribute data and “RAM” is added to the variable attribute data as attribute auxiliary information, as shown in FIG. A file is created as an analysis result table 801 of Class_A.
[0065]
  Then, the script generation means 802 converts the ROM designation or RAM designation file for each attribute data into a file 803 in which an intermediate language script is described, and the script expansion means 804 handles the compiler 805 based on the file 803. The source code file 807 corresponding to the language is converted.
[0066]
In the source code file 807, for example, the designation of const is given to the attribute data designated by ROM so that it cannot be changed at the time of execution, and the attribute data designated by RAM is accessed. A pointer is prepared to make the variable RAM area accessible.
[0067]
The compiler 805 uses the source code file 807 to create real machine software 806 for operating the real machine of the operating unit. The real machine software 806 uses the variable data in the attribute data of each object 1, 2, 3,. And a GUI configured by a plurality of objects whose invariant portions are stored in the ROM is obtained.
[0068]
In this way, since most of the objects can be stored in the ROM, the amount of expensive RAM used can be reduced, an inexpensive GUI operating device can be realized, and development efficiency can be improved. Can be planned.
[0069]
【The invention's effect】
  A graphical user interface operating device according to the present invention includes:A display object that has a plurality of screen objects composed of slide objects and icon objects corresponding to each display screen, controls the screen display based on the screen object specified from the plurality of screen objects, and detects a user operation A database object that manages various data including operation information and setting information of devices and systems subject to object control separately from display objects and manages them based on operation information on the display screen, and screen transition management based on each operation A procedure object that has a table, inputs an operation detected in the display object, and identifies a screen object corresponding to the display screen to be displayed next based on the screen transition management table based on the operation, and a display Once the operation information detected by the object is received Later, the data corresponding to the operation information output from the database object is received once and transmitted to the screen object of the display object specified by the procedure object via the slide object. Since it has a link object that displays a screen corresponding to the operation, it is possible to increase the independence of each object, and even when changing the procedure, only the procedure object needs to be changed, and the change and correction Can be easily performed. In addition, when performing similar control for each device to be controlled, the same operation procedure and screen creation work can be shared, so that the memory usage efficiency can be improved, The design efficiency can be improved.
[0071]
  Also, a graphical user interface according to the present inventionControllerThe operation is predicted after the data object consisting of multiple objects that separate the physical data used in the screen object of the display object from the display object and the screen object that generates the display screen. When one or more screen objects to be specified are specified by the procedure object, a corresponding screen object is extracted in advance based on the specification, and an object corresponding to the corresponding screen object is previously extracted from the data objects Since the memory management object generates one or more display screen data based on the extracted screen object and data object in advance, the time required for screen generation work can be reduced. , Actuator Can be improved and improved operability of the response.
[0072]
  Also, a graphical user interface according to the present inventionControllerThe procedure object calculates the transition probability of the display screen for the operation detected in the display object, and designates one or a plurality of screen objects whose operations are predicted next as memory management objects based on the transition probability. Therefore, the screen transition speed adapted to the user's operation tendency can be increased, and the response of the operating device can be improved and the operability can be improved.
[0073]
  Graphical user interface according to the present inventionControllerHas a decompression object that decompresses a pre-compressed data object as needed, so that the memory requirement for the entire data object can be reduced and the amount of expensive memory used can be reduced. it can.
[0074]
  Also, a graphical user interface according to the present inventionControllerWhen a screen object is specified by a procedure object, it has a decompression object that decompresses a data object corresponding to the image object out of pre-compressed data objects, thus reducing the amount of expensive memory used. In addition, the screen transition speed can be increased, and the response of the operating device can be improved and the operability can be improved.
[0075]
  Graphical user interface according to the present inventionControllerThe link object is a forward link object that links the display object and the database object and transmits the data of the display object to the database object, and a reverse direction that links the display object and the database object and transmits the data of the database object to the display object. Since the link object is included, the data exchange between the display object and the database object can be easily performed, and the data use range can be expanded.
[0076]
  Also, a graphical user interface according to the present inventionControllerHas an object management table that manages the correspondence between the object name and the address where each object exists, intervenes between the objects when sending a message, and identifies the address of the destination object based on the object management table Since each object has a message exchange service object that forwards a message to the object at that address, each object may be highly functionally independent without managing the address of the other party sending the message. In addition, it is possible to obtain a graphical user interface capable of realizing message communication with low memory and high flexibility in memory arrangement. Even when the memory arrangement of the object is changed, it is only necessary to change the object management table of the message exchange service object, so that the design efficiency of the graphical user interface can be improved.
[0077]
  Furthermore, the graphical user interface according to the present inventionControllerSince the message communicated between objects is composed of a fixed-length message consisting of a communication partner object name, a service number to be used, and a pointer address to a parameter to be exchanged between objects, the message communication process is easily performed. And enhance the overall functionality of the graphical user interface.
[0078]
  Graphical user interface according to the present inventionThe operation device has each objectOf the attribute data consisting of the variable part and the invariant part, the variable part is stored in the RAM and the invariant part is stored in the ROM, so that the amount of expensive RAM used can be reduced, and an inexpensive graphical user interface can be provided. It can be realized, and the development efficiency can be improved.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of first to tenth embodiments of the present invention.
FIG. 2 is a configuration explanatory diagram of a main part of the first embodiment of the present invention.
FIG. 3 is a configuration explanatory diagram of a display object and a data object according to the first embodiment of the present invention.
FIG. 4 is a configuration explanatory diagram of another main part of the first embodiment of the present invention.
FIG. 5 is a configuration explanatory diagram of another main part of the first embodiment of the present invention.
FIG. 6 is an operation explanatory diagram of a modified example of the link object according to the first embodiment of the present invention.
FIG. 7 is an operation explanatory diagram of another modified example of the link object according to the first embodiment of the present invention.
FIG. 8 is a configuration explanatory diagram of a main part of a second embodiment of the present invention.
FIG. 9 is an operation explanatory diagram of a main part of a second embodiment of the present invention.
FIG. 10 is a configuration explanatory diagram of a main part of a third embodiment of the present invention.
FIG. 11 is a configuration diagram of a screen transition management table and a transition probability management table of procedure objects according to the fourth embodiment of the present invention.
FIG. 12 is a configuration explanatory diagram of a main part of a fifth embodiment of the present invention.
FIG. 13 is a configuration explanatory diagram of a main part of an eighth embodiment of the present invention.
FIG. 14 is a configuration diagram of a reverse link management table for a reverse link object according to an eighth embodiment of the present invention and an explanatory diagram of a creation method thereof.
FIG. 15 is a configuration explanatory diagram of a main part of a ninth embodiment of the present invention.
FIG. 16 is a configuration diagram of a message communicated between objects.
FIG. 17 is a configuration diagram of a modified example of the object management table of the message exchange service object according to the ninth embodiment of the present invention.
FIG. 18 is an explanatory diagram of a method of realizing ROM or RAM storage for each attribute data of each object according to the tenth embodiment of the present invention;
[Explanation of symbols]
1 Display object, 2,24 Data object, 3,33 Database object, 4,47 Link object, 4a Reverse link object, 5 Procedure object, 6 Network management object, 7 Memory management object, 8 Expansion object, 9 Message exchange service Object, 9a Object management table, 17 Slide object, 18 Icon object, 25 Compressed data object, 100 GUI, 600 message, 601 Object name, 602 Service number, 603 Pointer to parameter.

Claims (9)

A display object having a plurality of screen objects composed of a slide object and an icon object corresponding to each display screen, controlling the screen display based on the screen object identified from the plurality of screen objects, and detecting a user operation;
A database object that manages various data including operation information and setting information of devices and systems to be controlled by the display object and manages them independently from the display object based on operation information on a display screen;
A screen object corresponding to the display screen to be displayed next based on the screen transition management table having the screen transition management table based on each operation, inputting the operation detected in the display object, and based on the screen transition management table based on the operation A procedure object that identifies the
The operation information detected by the display object is once received and transmitted to the database object, and the data corresponding to the operation information output from the database object is received once, and then specified by the procedure object. A link object that is transmitted to a screen object of a display object via a slide object and causes the screen object to display a screen corresponding to the operation ;
Of the attribute data of each object consisting of a variable part whose data contents are changed by the operation and an invariant part which is not changed, the variable part is stored in a RAM and the invariant part is stored in a ROM. Graphical user interface controller. A data object composed of a plurality of objects separated from the display object and made independent of physical data used in the screen object of the display object;
When one or a plurality of screen objects whose operation is predicted next to the screen object generating the display screen is specified by the procedure object, the corresponding screen object is extracted in advance based on the specification, 2. The graphical user interface operating device according to claim 1, further comprising: a memory management object for previously extracting an object corresponding to the corresponding screen object from the data objects.   3. The graphical user interface operating device according to claim 2, wherein the memory management object further generates one or a plurality of display screen data in advance based on the extracted screen object and data object.   The procedure object calculates the transition probability of the display screen for the operation detected by the display object, and designates one or more screen objects whose operations are predicted next based on the transition probability as the memory management object The graphical user interface operating device according to claim 2 or 3, characterized by:   5. The graphical user interface operating device according to claim 2, further comprising an expansion object that expands the data object that has been compressed in advance as needed.   5. The graphical object according to claim 2, further comprising a decompression object that decompresses a data object corresponding to the image object among the data objects compressed in advance when a screen object is specified by the procedure object. User interface controller.   The link object is a forward link object that links the display object and the database object to transmit the data of the display object to the database object, and links the display object and the database object to transmit the data of the database object to the display object. The graphical user interface operating device according to claim 1, 2, 3, 4, 5 or 6, further comprising a reverse link object.   It has an object management table that manages the correspondence between the object name and the address where each object exists, intervenes between the objects when sending a message, specifies the address of the destination object based on the object management table, and 8. The graphical user interface operator according to claim 1, further comprising a message exchange service object for transferring a message to an address object.   9. The graphical user according to claim 8, wherein a message communicated between objects is constituted by a fixed-length message comprising a communication partner object name, a service number to be used, and a pointer address to a parameter exchanged between the objects. Interface controller.

Images