JPH02139626A - Multiwindow event management device - Google Patents

Abstract

PURPOSE:To automatically switch the active state of a window by collectively and uniformly managing event information generated by the operation of a user, message information for control of windows, and message information for information exchange between windows to perform the control. CONSTITUTION:A window event managing means 20 uses a window information managing means 14 to confirm states of windows managed by the application process which issues an event acquisition request. The window information managing means 14 retrieves list structure data indicated by an address indicating part 30 and checks a window ID storage part 32 and returns the state of the window stored in a window state storage part 36 of element data having a designated window ID to the window event managing means 20. Based on information returned from the window information managing means 14, the managing means 20 automatically transfers the control to the active processing or the non-active processing when the window is in the active state or the non-active state.

Description

[Detailed Description of the Invention] Industrial Application Field The present invention relates to a multi-window event management device that performs input event processing and window control for a small computer system (personal computer) that implements multi-window display. . In particular, events that occur from user operations and the computer system operations associated with these operations, as well as message information for controlling windows and message information for exchanging information between windows, can be centrally summarized. The present invention relates to a multi-window event management device.

BACKGROUND ART FIG. 11 shows the configuration of an event management means of a conventional small computer system (personal computer), in which 1 is a keyboard, 2 is a pointing device, 3 is a floppy disk, and 4 is a keyboard or pointing device. A device management means that detects the occurrence of an event from the device 2 or the floppy disk 3 and manages the detected event as event information in a queue; 5 creates window control information that notifies a window redisplay instruction or a change in the window active state; 6 is a device management means 4 and a window management means 5.
This is an event management device that manages events in a unified manner using

The operation of the conventional personal computer configured as described above when performing event processing will be explained using the flowchart shown in FIG.

When an application process acquires event information in the above system, the application process sends an event acquisition command to the event management means 6.

At step 7, the event management means 6 uses the window management means 5 to check whether window control information exists. The window control information includes an active state change message indicating that the window has moved to the active state, which is a state in which the window can obtain event information from the keyboard or pointing device, and an inactive state change message, which is the opposite state. , a redisplay message that instructs to redisplay the window, etc. If this window control information exists, the process moves to 8; if it does not exist, the process moves to 9.

At 8, the event management means 6 extracts the window control information using the window management means 5, sends the window control information to the application process, and ends the process.

In 9, the event management means 6 is connected to the device management means 4.
is used to extract the event information managed in the queue, and if event information exists, send this event information to the application process and end the process. When event information does not exist, event information indicating that no event information has occurred is generated and the process ends.

Problems to be Solved by the Invention However, with the above configuration, there is a problem in that after the application process takes in event information from the event management means 6, it is necessary to analyze the event information by itself and operate according to the content of the analysis. It had a point.

For example, the application process uses the acquired event information and window position information to change the shape of the pointer itself, and converts the event occurrence position information recorded in the event information to another coordinate system. , there is a problem in that the menu selection function must be started based on the event location information recorded in the event information and the state of the pointing device switch, and the user must also exchange message information between windows. Was.

In view of the above, the present invention provides event information generated from user operations and computer system operations accompanying those operations in a multi-window system, and message information for controlling windows and messages for exchanging information between windows. It manages information centrally and automatically changes the pointer shape, converts the event position information to another coordinate system, analyzes the event information, and selects a menu selection event if it matches the specified situation. An object of the present invention is to provide a multi-window event management device that automatically generates a window and automatically switches the active state of a window.

Means for Solving the Problems The present invention provides an event management means for managing an event generated from an input device as event information including the time at which the event occurred and the position information of a pointer at the time the event occurred, and a window. window information management means for storing and managing the attributes of the window; active window switching means for switching the active state to a specific window; and the location in memory of message information that gives window control instructions to the window and the window to which the message information should be sent. Message information management means for storing and managing a number indicating the message information, a pointer shape changing means for changing the shape of the pointer according to the relationship between the position information of the pointer and the position of the currently active window, and an event managed by the event management means. A coordinate conversion means that converts the event occurrence position information recorded in the information into a specified coordinate system, and any function can be registered as a front-end function, and event information is sent to the specified front-end function. , front-end processor means for receiving event information processed by the functions thereof, event management means, coordinate conversion means, window information management means, active window switching means,
This multi-window event management means is characterized by comprising a window event management means that controls the message information management means and the front end processor means and centrally manages event information and message information.

Effect of the present invention With the above-described configuration, the present invention can centrally manage and control event information that occurs due to user operations, message information that controls windows, and message information that exchanges information between windows. Message information can be exchanged between windows, the pointer shape is automatically changed, the coordinates of the location information recorded in event information are converted, and event information that requests menu selection is automatically generated and registered when the conditions are met. The event information is processed by sending the event information to the front-end function that has been created, and receiving the processed event information from that function, and the active state of the window is switched based on the position information where the event occurred and the window position information. do.

Embodiment FIG. 1 shows the configuration of a multi-window event management apparatus according to an embodiment of the present invention. In FIG. 1, 10 is a keyboard, 11 is a floppy disk driver, and 12 is a pointing device. 13 is the keyboard 10. Events generated from input devices such as the floppy disk driver 11 and the pointing device 12 are summarized as event information including the time of occurrence and the position of the pointer at one point when the event occurred, and the event information is managed in a queue and the pointing device 12 This is an event management means for changing event information to a menu selection event by a combination of switches attached to the pointing device 12. 14 is a window information management means for managing and storing window attributes such as window size and position on the screen; 15 is an active window switching means for switching the active state of a specified window; and 16 is message information for managing messages for each window. It is a means of control. Reference numeral 17 denotes a coordinate conversion means for converting the position information recorded in the event information managed by the event management means 13 into a specified coordinate system, and 18 refers to the shape of the pointer by converting the shape of the pointer into the position information of the pointer and the position of the currently active window. Pointer shape changing means 19 is a front-end processor means that sends event information to a designated function and receives event information processed by the function.

20 is an event management means 13, a coordinate conversion means 17, a pointer shape changing means 18, and a window information management means 14.
, active window switching means 15 , message information management means 16 , and front end processor means 19
This is a window event management means that centrally manages event information and message information.

FIG. 2 shows the structure of event information returned by this multi-window event management device. 21 is an event type indicating the type of event information such as keyboard, pointing device, redisplay of window, switching of active state of window (change to active state or change to inactive state). 22 is the event occurrence time indicating the time when the event information occurred, 23 is the event occurrence position indicating the position on the screen where the event information has occurred, and 24 is, for example, if the event information is generated from the keyboard, information about the pressed key, voting For event information generated from a device, this is event detailed information that shows detailed event information such as information on pressed buttons.

FIG. 3 shows the structure of window attribute data managed by the window information management means 14. The window information management means 14 manages window information in a list structure, and assigns one window information to one element of the list structure. The elements in the list structure are arranged according to the overlap of the windows, starting with the element corresponding to the window located at the forefront of the screen, and continuing with the elements corresponding to the windows according to the overlap of the windows.

30 is an address instruction section indicating the beginning of the list structure data;
31 to 37 indicate the structure within the element of list structure data. 31 is a next address storage unit that indicates the address where the next element exists; 32 is a window ID storage unit that stores the identifier of the window indicated by this element; and 33 is a process ID that indicates the process that manages the window indicated by this element.
A storage unit 34 is a window position storage unit that stores the position of the window indicated by this element on the screen, 35 is a window size storage unit that stores the size of the window indicated by this element, and 36 is the state of the window indicated by this element. A window state storage unit 37 stores the type of window indicated by this element (for example, a window whose size cannot be changed, a window whose size cannot be moved, a window whose active state is This is a window type storage unit that stores information such as windows that are retained until they are closed.

FIG. 4 shows the structure of the message information management means 16. The message information management means 16 is composed of a plurality of storage sections, each of which is composed of two storage registers.

Reference numeral 40 denotes an index section for storing a window ID for sending a message, and reference numeral 41 denotes an address designation section for indicating the start address of message information managed in a list structure.

The message information management means 16 manages message information for each window designated by the index section 40 in a list structure.

FIG. 5 shows the data structure of message information managed by the message information management means 16 in a list structure.

42 is an address instruction section that indicates the first address to the list structure data; 43 is an attribute section that stores message attributes;
44 is a next address storage section that stores the address to the next message element data; 45 is a data size storage section that stores the size of the message data; and 46 is actual data in which actual message data is stored.

The operation of the multi-window event management device of this embodiment configured as described above will be described below.

The operation of this embodiment when an application process issues an event acquisition request to a multi-window event management device in a multi-window system will be described.

The operation of the multi-window event management device of this embodiment will be explained using the flowchart shown in FIG.

It is assumed that the application process always issues an event acquisition request by indicating the window ID of the window managed by the application process. It is also necessary to specify whether the acquired event position information is to be coordinate-transformed to match the coordinates of the currently active window, or whether it is a through mode in which coordinates are not transformed.

Furthermore, when an event occurs at a position where the active state of a window should be changed, whether the active state is changed to changeable mode or unchangeable mode, and when the active state is lost, other A message waiting mode in which message information is waited until message information is received from the application process or the window event management means 20 or a message not waiting mode shall also be specified.

At 50, the window event management means 20 uses the window information management means 14 to confirm whether the window managed by the application process that issued the event acquisition request is in an active state or an inactive state. The window information management means 14 searches the list 1tVt structure data indicated by the address instruction section 30, checks the window ID storage section 32 in each list element data, and determines the window state of the element data having the specified window ID. The state of the window (active state or inactive state) stored in the storage unit 36 is returned to the window event management means 20.

If the window is in the active state based on the information returned from the window information management means 14, the window event management means 20 transfers control to active processing 51. If the window is inactive, processing moves to the inactive process 52.

At the end of this process, event information having the structure shown in FIG. 2 is returned to the application process.

The active process will be explained using the flowchart of FIG.

At 60, the window event management means 20 first uses the message information management means 16 to check whether message information exists for the window managed by the application process that issued the event acquisition request.

The message information management means 16 investigates the message information using the address designation section 41 corresponding to the index section 40 that matches the designated window. If the address designation section 41 is 0, the message information management means 16 reports to the window event management means 20 that message information for the specified window does not exist. If the address exists in the address instruction section 41, the existence of the message is reported to the window event management means 20.

If a message exists based on the report from the message information management means 16, the window event management means 20 moves the process to 61. If it does not exist, the process moves to 63.

At 81, the window event management means 20 uses the message information management means 16 to extract message information for the specified window.

The message information management means 16 sends the message information of the first element of the list structure data indicated by the address instruction section 41 corresponding to the specified window to the window event management means 20.

After obtaining the message information from the message information management means 16, the window event management means 20 performs processing at 64.
Move to.

At 63, the window event management means 20 uses the event management means 13 to input event information generated from the input device. The event management means 13 returns the queue-managed event information from the keyboard, floppy disk, or pointy device to the window event management means 20 in FIFO order. Note that the event information managed by the event management means 13 already includes the following information:
The event occurrence time and the position of the pointer on the screen at the time of the event occurrence are recorded. Further, when the event management means 13 receives an event generated by a switch attached to a pointing device, it checks the combination of the switches and processes the event into a menu selection event that requests menu selection processing when a specific combination is found. .

At 64, the window event management means 20 checks whether the front end function is registered with the front end processor means 19.

If the front end function is registered, process 65.
Control is then transferred to the front end processor means 19. If the front end function is not registered, the process moves to 66.

At 65 the front end processor means 19
The event information or message information obtained through the processes up to 4 is passed to the registered front-end function. The event information or message information processed by the front-end function is returned from the front-end function to the front-end processor function 65 again, and processing is moved to 66.

At 66, the window event management means 20 uses the pointer shape changing means 18 to change the shape of the pointer. The pointer shape changing means 18 uses the position information recorded in the event information and the position information of the currently active window obtained from the window information management means 14 to change the shape of the pointer according to the position of the active window. Execute. Note that the message information is processed by 67, where this process is performed.

At 67, the window event management means 20 moves the process to 71 if the current processing target is message information or a menu selection event. If the current processing target is not message information or menu selection event, process 6.
Move to 8.

At step 68, the window event management means 20 uses the window information management means 14 to check on which window the event occurred using the position information recorded in the event information. The window information management means 14 uses the position information recorded in the event information to set the window attribute data of the list structure shown in FIG. The position storage section 34 is checked, and the window ID recorded in the window ID storage section 32 of the matching element of the window position storage section 34 is returned to the window event management means 20.

At 69, the window event management means 20 moves the process to window change processing at 70 if the position where the event information has occurred is not on the currently active window. If the event information occurs on the currently active window, the process moves to 71.

At 70, the window event management means 20 uses the active window switching means 15 to make the window in which the event information has occurred active, and makes the previously active window inactive. Next, the overlapping relationship between the windows is changed along with the change in the active state, the newly activated window is brought to the forefront, and an instruction to redisplay the window is also issued accordingly.

At step 71, the window event management means 20 sends the event information or message information that has been processed up to now to the application process, and ends the processing.

The event transmission process will be explained using the flowchart of FIG.

At 80, the window event management means 20 confirms whether the option setting at the time of event acquisition of the application process is a mode in which the coordinates are converted according to the coordinates of the currently active window, or a through mode in which coordinates are not converted. If the mode is coordinate transformation mode, the process moves to 81, and if it is the through mode, the process moves to 82.

At 81, the window event management means 20 uses the window information management means 14 to extract position information of the currently active window.

Next, the window event management means 20 converts the position information recorded in the event information into the coordinate system of the active window using the position information of the active window and the coordinate conversion means 17.

At 82, the window event management means 20 passes the ``tff'' information to the application process and ends the process.

The window change process will be explained using the flowchart of FIG.

At 90, the window event management means 20 checks whether the option setting at the time of event acquisition of the application process is a mode in which the active state of the window can be changed or a mode in which it cannot be changed. If the active state is the changeable mode, the process moves to 92. If the active state cannot be changed, the process moves to 91.

At 91, the window event management means 20 performs an event transmission process to the application process, and ends the process.

At 92, the window event management means 20 uses the active window switching means 15 to perform a process of switching the active state of the window for the window that is newly set to the active state. The active window switching means 15 is the window event management means 2.
When a window to be newly activated is specified from 0, the window information management means 14 is used to change the window status storage unit 36 of the element corresponding to the specified window in the window attribute data to the active status, and the previous window is changed to the active status. The window state storage unit 36 of the element for the window that was in the active state is set to the inactive state.

At 93, the active window switching means 15 moves the newly activated window to the forefront. Therefore, the active window switching means 15 changes the list structure of the window management information held by the window information management means 14, and creates a list structure in which the element corresponding to the newly activated window is directly indicated by the address instruction section 30. Move to the first position.

At step 94, the active window switching means 15 determines the window and redisplay area that need to be redisplayed due to the change in the overlapping relationship of the windows. Next, the active window switching means 15 is activated by the message information management means 1.
6 is used to set a redisplay message for the window that needs to be redisplayed and a message for changing the active state to the window that has become active. Then, the event type of the event information that caused the window switching is changed to "change to inactive state", and the process ends.

The inactive process will be explained using the flowchart of FIG.

At step 100, the window event management means 20 confirms whether the mode is a message waiting mode in which the message information waits until message information arrives or a message not waiting mode. When the window event management means 20 waits for a message, the process moves to 102. If the mode is not to wait for messages, the process moves to 101.

At step 101, the window event management means 20 uses the message information management means 16 to check whether message information has arrived for the specified window. If message information has arrived, the window event management means 20 moves the process to 104.

At step 102, the window event management means 20 uses the message information management means 16 to check whether message information has arrived for the designated window. If message information has arrived, the window event management means 20 moves the process to 104. If the message information has not yet arrived, the window event management means 20 performs processing 1.
Move to 03.

At step 103, the window event management means 20 continues to wait until message information arrives for the window specified using the message information management means 16. Then, when the message information arrives, the process moves to 104.

At 104, the window event manager 20 passes the message information to the application process. Then, the process ends.

At step 105, the window event management means 20 creates "No message information" indicating that there is no message information for the designated window and returns it to the application process. Then, the process ends.

As described above, according to the present embodiment, an event management means for managing an event generated from an input device as event information including the time at which the event occurred and the position information of a pointer at the time at which the event occurred; A window information management means for storing and managing window attributes, an active window switching means for switching the active state to a specific window, and a memory location of message information for giving window control instructions to the window and message information to be sent. Message information management means for storing and managing numbers indicating windows; pointer shape changing means for changing the shape of the pointer according to the relationship between pointer position information and the position of the currently active window; and events managed by the event management means. A coordinate conversion means that converts the event occurrence position information recorded in the information into a specified coordinate system, and any function can be registered as a front-end function, and event information is sent to the specified front-end function. , controls front-end processor means that receives event information processed by its functions, event management means, coordinate conversion means, window information management means, active window switching means, message information management means, and front-end processor means, Equipped with a window event management means that centrally manages information and message information, it is possible to compile event information generated by user operations, message information for controlling windows, and message information for exchanging information between windows. By centrally managing and controlling it, you can freely exchange message information between windows, automatically change the pointer shape, perform coordinate transformation of position information recorded in event information, and request menu selection. Event information is automatically generated when the conditions are met, and the event information is processed by sending the event information to the registered front-end function and receiving the processed event information from that function. The active state of the window can be switched based on the position information.

Note that in the above embodiment, the window information management means 14
Although the data management method of the message information management means 16 is realized using a list structure, it may also be realized using an array type data structure.

DETAILED DESCRIPTION OF THE INVENTION According to the present invention, event information generated by user operations, message information for controlling windows, and message information for exchanging information between windows can be centrally managed and controlled. By doing so,
You can freely exchange message information between windows, automatically change the pointer shape, perform coordinate transformation of position information recorded in event information, automatically generate event information that requests menu selection when conditions are met, The event information is processed by sending event information to the registered front-end function and receiving the processed event information from that function, and switching the active state of the window based on the position information where the event occurred and the window position information. can be carried out, and its practical effects are significant.

[Brief explanation of the drawing]

FIG. 1 is a block diagram of a multi-window event management device according to an embodiment of the present invention, FIG. 2 is a block diagram of window event data, FIG. 3 is a block diagram of window information management means, and FIG. 4 is a block diagram of a message management device. Configuration diagram of information management means,
Fig. 5 is a structural diagram of message information data, Fig. 6 is a flowchart showing the operation of the multi-window event management device, Fig. 7 is a flowchart of active processing, and Fig. 8 is a flowchart showing the operation of the multi-window event management device.
Figure 9 is a flowchart of event sending processing, Figure 9 is a flowchart of window change processing, Figure 10 is a flowchart of inactive processing, Figure 11 is a configuration diagram of a conventional event management device, and Figure 12 is conventional event management. It is a flowchart explaining the operation of the device. 10: Keyboard, 11: Floppy disk driver, 12: Φ pointing device, 13: Event management means, 14: Window information management means, 15Φ: Active window switching means,
16・φ・Message information management means, 17・Coordinate conversion means, 18・φ・Pointer shape changing means, 19・・0
Front end processor means, 200φ/window event management means, 21... event type, 22...
Event occurrence time, 23...Event occurrence position, 24
・・Contest event details information, 30@-work address instruction section,
31 fist...Next address storage section, 32...Window I
D storage section, 33... Process ID storage section, 34... Fist window position storage section, 35... Window size storage section, 36... φ window state storage section, 37... Window type storage section, 40 ...Index section, 41
・Fist/Address instruction part, 42...Address finger umbrella part, 4
3.Φ-attribute section, 44...Next address storage section, 45.
...Data size storage section, 46...Actual data. Name of Agent Patent Attorney Shigetaka Awano Figure 13 Figure Figure Figure Figure Funeral Figure Figure 1O Figure Figure

Claims (7)

[Claims] (1) Events generated from input devices such as keyboards, pointing devices, floppy disk drivers, etc. are recorded as the time at which the event occurred and the position information of the pointer that moves on the screen in conjunction with the pointing device at the time the event occurs. An event management method that collectively manages event information, window size,
a window information management means for storing and managing window attributes such as a position on the screen and an ID of a process managing the window; and an active state in which the process managing the window can receive event information from the input device. An active window switching means that performs the processing of switching to a specific window, and a message information that provides window control instructions such as redisplaying the window contents or changing the active state to the process that manages the window, and sending the message information to the specified window. a message information management means for managing the
pointer shape changing means for changing the shape of the pointer according to the relationship between the position information of the pointer on the screen and the position of the currently active window; a coordinate conversion means for converting to a specified coordinate system;
a front-end processor means capable of registering any function, and processing event information by sending event information to the registered function and receiving event information processed by the function; and the event management means; Window event management means for controlling the coordinate conversion means, the window information management means, the active window switching means, the message information management means, and the front end processor means, and for centrally managing event information and message information. A multi-window event management device characterized by: (2) Events generated from input devices such as keyboards, floppy disk drivers, pointing devices, etc. are combined with the event occurrence time and pointer position information at that time to create event information, and the event information is queue-managed, and the pointing device A menu selection event, which is event information that requests menu selection, is generated based on the event information from the switches attached to the switch, and when an event acquisition command is received from the application process, the event information that is managed in the queue is generated. 2. A multi-window event management device comprising the event management means according to claim 1, which sends event information at the beginning of the event information to a request destination. (3) Converting the position information of the pointer on the screen linked to the pointing device recorded in the event information managed by the event management means to match the coordinate system of the specific window stored in the window information management means. The multi-window event management device according to claim 1, further comprising coordinate conversion means. (4) The shape of the pointer on the screen that is linked to the pointing device is determined based on the event occurrence position information recorded in the event information and the position of the active window where event information can be obtained from input devices such as the keyboard and pointing device. 2. The multi-window event management device according to claim 1, further comprising pointer shape changing means for changing the shape using information. (5) If the active state of a window is specified as switchable, in the event information that occurs when a pointing device is switched managed by the event management means, an event caused by a pointing device switch within another window that is not in an active state. When information occurs, the active state is switched to the window where the event information occurred, and at the same time, the overlapping relationship of the windows is changed, the newly activated window is moved to the front, and the window content is changed by switching the overlapping relationship of the windows. If redisplay is necessary, send the redisplay message information to the necessary windows.
2. The multi-window event management device according to claim 1, further comprising active window switching means for sending messages using message information management means. (6) It has a structure that stores and manages both the memory location of message information and the number indicating the window to which the message information should be sent, manages the message information sent to the specified window in a queue, and requests the application process. Reports whether there is message information for the specified window, sends the message information for the specified window to the application process, waits until a message arrives if the message information wait mode is specified, and returns the message information. 2. The multi-window event management device according to claim 1, further comprising message information management means for sending the message information to the requesting application process after the message information arrives. (7) You can register any front-end function that inputs event information and processes that event information, and reports the registration status to the application process that requested the registration status of the front-end function. 2. The multi-window event system according to claim 1, further comprising front-end processor means for sending event information to a registered front-end function when the event information is registered and receiving event information processed by the front-end function. Management device.