JPH03186920A - Keyboard control system - Google Patents

Abstract

PURPOSE:To convert make information into make information which does dot generate malfunction and into brake information by storing break information which is simulatory generated by means of make information immediately before in a queue buffer in correspondence with the input of make information of a key which does not generate break information from a keyboard or after prescribed time elapses. CONSTITUTION:Break information which make information artificially generates immediately before is stored in the queue buffer 3 in correspondence with the input of make information of the key which does not generate brake information from the keyboard 2 or after prescribed time elapses. Then, key input information is taken out from the queue buffer 3 and supplies information to a system which requires break information. Thus, conversion into make information which does not generate malfunction and break information from make information is attained among key input information which is key-inputted by the keyboard 2 used under multi-OS.

Description

[Detailed Description of the Invention] [Summary] Regarding a keyboard control method that generates break information based on make information from the keyboard, it is possible to respond to the input of make information of keys that do not generate break information from the keyboard or for a predetermined period of time. After the elapsed time, the break information generated pseudo-generated from the previous make information is stored in the queue buffer,
The purpose is to convert make information into make information and break information that do not cause malfunctions, and there is a queue buffer that stores key input information input from the keyboard, and make information for keys whose key input information does not generate break information. A break notification register is provided to store break information generated when the break information is generated, and in response to a notification of make information from a key that does not generate break information from the keyboard, when break information is stored in the break notification register. is extracted and stored in the above queue buffer, the make information is stored in the queue buffer, the generated break information is stored in the above break notification register, and when break information is stored in the break notification register after a predetermined period of time, is retrieved, stored and cleared in the queue buffer, key input information is retrieved from the queue buffer, and the break information is notified to a system that requires it.

[Industrial application field]

The present invention relates to a keyboard control method that generates break information based on make information from keyboard 1. In recent years, with the diversification of computers, it has become possible to simultaneously operate two or more types of O3 (operating systems) in one device. In general, the format of the key input information from the keyboard is a format that is conscious of the O3 that primarily operates, and may be different from the format that is conscious of the other O3 that operates as a secondary device. In this different case,
Key input information from the keyboard is converted and notified to O3, which operates as a sub-server.

[Conventional technology]

Key input information from the keyboard includes the following.

(11 Which key (key address)? (2) Are modifier keys such as the shift key or control key pressed at the same time? (3) Are they pressed (make information, make information wA),
Is it released (break information, brake information), or continues to be pressed (tiebamatic information, typer information)?
magic information) The conversion of the key input information in (1), (2), and (3) can be performed using a conversion table or a simple conditional statement, and there is no problem even under a multi-OS system.

However, in order to reduce the load on the CPU from the keyboard, there is a system in relatively high-end computer systems that does not generate break information for keys other than specific keys such as modifier keys such as shift keys and control keys, thereby reducing the load on the CPU. do. On the other hand, low-cost systems such as personal computers often use break information for all keys. Therefore, in a multi-OS system, if the main O3 does not use break information for a specific key, and the secondary O3 uses break information for all keys, key input information from the keyboard For the make information of a key that does not generate break information, break information is generated in a pseudo manner to form a pair (make information + break information), and the pair (make information + break information) is notified to the O3, which operates as a sub-key.

[Problem to be solved by the invention]

In this way, the OS that mainly operates from the keyboard 1
In the case of a system where the key input information for the system does not generate break information, make information and break information are generated at the same time, they are paired, and the information is notified to the O3 that operates as a sub. There was a problem that the application program would malfunction. For example, in order to pursue real-time performance such as in a game, O3, which operates as a sub-server, skips the middle of the key input information stored in the queue buffer and expects the make information of a specific key at the end, as described above. In the conversion, the make information from the keyboard is converted to make information +
Because it was converted into break information, there was a problem that no matter how long it ended, it would be break information and not make information, and it would remain stopped and not move.

The present invention corresponds to the input of make information from the keyboard for keys that do not generate break information, or after a predetermined period of time has elapsed, stores break information that is pseudo-generated from the previous make information in a queue buffer, and malfunctions based on the make information. The purpose is to convert it into make information and break information that does not occur.

[Means to solve problems]

FIG. 1 shows a basic configuration diagram of the present invention.

In FIG. 1, CPLll processes key input information from the keyboard 2. In FIG.

The queue buffer 3 is a buffer that temporarily stores key input information input from the keyboard 2 and the like.

The timer 4 is a timer that generates an interrupt to the CPUI at predetermined intervals and starts a routine that retrieves break information from the break notification register 5, stores it in the queue buffer 3, and clears it.

The break notification register 5 is a register that stores break information pseudo-generated from make information.

[Effect]

As shown in FIG. 1G, the present invention retrieves break information when it is stored in the break notification register 5 in response to a notification of make information of a key that does not generate break information from the keyboard 2. The make information is stored in the queue buffer 3, and the generated break information is stored in the break notification register 5. When break information is stored in the break notification register 5, it is retrieved, stored in the queue buffer 3, and cleared, key input information is retrieved from the queue buffer 3, and the system that requires the break information is notified. ing.

Therefore, in response to input of make information from a key that does not generate break information from the keyboard '2, or after a predetermined period of time has elapsed, break information generated pseudo-generated from the previous make information is stored in the queue buffer, and from this queue buffer. By extracting key input information and notifying the system that requires the break information, it becomes possible to convert the make information into make information and break information that do not cause malfunctions.

〔Example〕

Next, the configuration and operation of one embodiment of the present invention will be explained in detail using FIGS. 2 and 3.

In FIG. 2, CPUI is a processor that operates on the main O8, and is a processor that processes key input information from the keyboard 2. Here, the CPUI is a processor that does not use break information for specific keys from the keyboard 2 (keys other than modifier keys such as shift keys and control keys).

The keyboard 2 is used by the user to key-input various data. When a key is input from the keyboard 2, the CPU 1 is notified of this by an interrupt, and the process shown in FIG. 3, which will be described later, is performed regarding the key input information.

The queue buffer 3 is a buffer that temporarily stores key input information input from the keyboard 2 and the like.

The timer 4 is a timer that generates an interrupt to the CPUI at predetermined intervals and activates a routine that retrieves break information if it is stored in the break notification register 5, stores it in the queue buffer 3, and clears it.

The break notification register 5 is a register that stores break information pseudo-generated from make information.

The CPU 6 is a processor that operates as a sub-O3, and when it wants to use key input information from the keyboard 2, it notifies the CPU 14 of this by an interrupt, and via the queue buffer 3, CPtJl, and communication register 7,
It receives key input information from the keyboard 2 and pseudo-generated break information.

The communication register 7 is a communication register for receiving key input information and the like from the CPU 1.

Next, the operation of the configuration shown in FIG. 2 will be explained in detail using the flowchart shown in FIG.

FIG. 3(a) shows a processing flowchart of key input information.

In FIG. 3(A), the OC determines whether it is necessary to generate break information. This is done by referring to a table (not shown) or the like to determine whether or not the make information keyed in from the keyboard 2 in FIG. 2 is the make information of a key that generates break information. If YES (make information for a key that does not generate break information),
@I do.

If NO (if it is make information for a key that generates break information), press ■ to add keyboard 2 to the queue buffer.
The key input information (make information, break information, tiebamatic information of the key that generates break information) input from the key is stored, and the process ends.

@ determines whether the break notification register is empty or not. Y
In the case of ES (if no pseudo-generated break information is stored in the break notification register 5), process (1) is performed. If No (if the pseudo-generated break information is stored in the break notification register 5), the break notification register 5 is stored in [phase].
The break information stored in is stored in the queue buffer 3, and step (2) is performed.

0 stores make information in the queue buffer.

(2) stores break information in the break notification register. This stores the make information keyed in from the keyboards 1 and 2 in the queue buffer 3 at 0, and then stores the break information generated in a pseudo manner in the break notification register 5.

Through the above steps, the key input information is processed.

Next, FIG. 3(b) shows a processing flowchart according to the interrupt routine.

In FIG. 3 (part), the timer interrupts the CPU1.

(2) determines whether or not the time has expired. If YES (after storing the break information pseudo-generated in Fig. 3 (a) ■ in the break notification register 5, for example, if the time exceeds about 20 ms to 500 ms), perform ■. . In the case of No, repeat ①.

(2) Determines whether the break notification register is not empty. If YES (when break information is stored in the break notification register 5), the break information stored in the break notification register 5 is retrieved and stored in the queue buffer 3 in ■, the process is cleared, and the process ends. do. If NO (if no break information is stored in the break notification register 5), the process ends without doing anything.

As described above, if the break information has been stored in the break notification register 5 for a predetermined period of time (approximately 20 ms to 500 ms), this break information is transferred to the queue buffer 3.
Store and clear. Then, the make information, break information, and typermatic information stored in the queue buffer 31 are notified to the CPU 6 operating in the sub-O3.

〔Effect of the invention〕

As explained above, according to the present invention, in response to the input of make information of a key that does not generate break information from the keyboard 2, or after a predetermined period of time has elapsed, break information generated in a pseudo manner from the previous make information is queued. Key input information is stored in the buffer 3, retrieved from this queue buffer 3, and notified to the system that requires the break information, so the key input information input using the keyboard 2 used under the multi-O3 Of these, the make information can be converted into make information and break information that do not cause malfunctions.

[Brief explanation of drawings]

FIG. 1 is a diagram showing the principle of the present invention, FIG. 2 is a diagram showing the construction of an embodiment of the present invention, and FIG. 3 is a flowchart explaining the operation of the present invention. In the figure, 1.6 is a CPU, 2 is a keyboard, 3 is a queue buffer (FIFO type), 4 is a timer, 5 is a break notification register, and 7 is a communication register.

Claims (1)

[Claims] In a keyboard control method that generates break information based on make information from a keyboard, a keyboard (2)
A queue buffer (3) that stores key input information etc. input from the key input information, and a break notification register (5) that stores break information generated when the key input information is make information for a key that does not generate break information. , in response to notification of make information from the keyboard (2) for keys that do not generate break information, when break information is stored in the break notification register (5), it is retrieved and sent to the queue buffer (3). Store the make information in the queue buffer (
3) and the generated break information is stored in the break notification register (5), and when the break information is stored in the break notification register (5) after a predetermined period of time, it is retrieved and stored in the queue buffer. (3) Store and clear key input information from the queue buffer (3), and notify break information to a system that requires it.