JPH07120234B2 - Keyboard control system - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION [Outline] The present invention relates to a keyboard control method for generating break information based on make information from a keyboard, which corresponds to input of make information of a key not generating break information from a keyboard or at a predetermined time. After the lapse of time, the pseudo-generated break information of the immediately preceding make information is stored in the queue buffer, and the purpose is to convert the make information into make information and break information that does not cause malfunctions. A break notification register that stores the break information generated when the key input information is the make information of the key that does not generate the break information, and the break information register of the key that does not generate the break information from the keyboard. In response to the notification, break to the break notification register above. When information is stored, it is taken out and stored in the above queue buffer, make information is stored in the queue buffer,
And the generated break information is stored in the break notification register, and when the break information is stored in the break notification register after a lapse of a predetermined time, it is taken out and stored and cleared in the queue buffer. It is configured to take input information and notify the system that requires break information.

[Industrial application field]

The present invention relates to a keyboard control system for generating break information based on make information from a keyboard. With the recent diversification of computers, two or more types of OSs (operating systems) have been simultaneously operated in one device. Generally, the format of the key input information from the keyboard is a format that is mainly conscious of the operating OS, and may be different from the format that another OS operating as a subordinate is aware of. In the case of this difference, the key operating information from the keyboard is converted and notified to the OS operating as a subordinate.

[Conventional technology]

 Key input information from the keyboard is as follows.

(1) Which key (key address) (2) Simultaneous pressing of modifier keys such as shift key and control key (3) Whether they were pressed (make information, make information) or released (break information, break information) Information), and whether or not the key is pressed continuously (typmatic information, typer matic information) The conversion of the key input information of (1), (2), and (3) is performed using a conversion table or a simple conditional statement. It is possible, and there is no problem even under a multi-OS system.

However, in order to reduce the load on the CPU side by the keyboard, break information is not generated for keys other than specific keys such as modifier keys such as shift keys and control keys, and there is a system in a relatively high-class computer system that reduces the CPU load. To 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, the OS that operates mainly does not use the break information for a specific key, and the OS that operates as a sub
Is a system that uses the break information of all keys, the break information of the key input information that does not generate the break information of the key input information from the keyboard is artificially generated as the break information (make information + break information). And, I was trying to notify the OS operating as a sub.

[Problems to be Solved by the Invention]

In this way, in the case of a system in which key input information from the keyboard to the operating OS does not generate break information, make information and break information are generated at the same time, and these are paired and notified to the OS operating as the sub. As a result, there is a problem that the application program that runs under the OS that runs as a subordinate operates abnormally. For example, if the OS operating as a subordinate skips the middle of the key input information stored in the queue buffer and expects the make information of the last specific key in order to pursue real-timeness like a game, In the exchange, the make information from the keyboard was converted into make information + break information, so there was a problem that the last piece of break information was break information and it was not make information, and it stopped and did not move.

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 or after a predetermined time has elapsed, the pseudo generated break information of the immediately preceding make information is stored in the queue buffer, and a malfunction occurs from the make information. The purpose is to convert to make information and break information that does not generate.

[Means for solving the problem]

 FIG. 1 shows the principle configuration of the present invention.

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

The queue buffer 3 is a buffer for temporarily storing key input information input from the keyboard 2.

The timer 4 is a timer that causes the CPU 1 to generate an interrupt at predetermined intervals, extracts break information from the break notification register 5, and stores and clears the break information in the queue buffer 3.

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

[Action]

According to the present invention, as shown in FIG. 1, when the break information is stored in the break notification register 5 in response to the notification of the make information of the key which does not generate the break information from the keyboard 2, the break information is taken out. The break information is stored in the queue buffer 3, the make information is stored in the queue buffer 3, the generated break information is stored in the break notification register 5, and the break information is generated in the routine activated by the interrupt from the timer 4 to the CPU 1 at predetermined intervals. Notification register 5
When the break information is stored in, the queue information is taken out, stored and cleared in the queue buffer 3, and the key input information is taken out from the queue buffer 3 to notify the system that requires the break information.

Therefore, in response to the input of make information of a key that does not generate break information from the keyboard 2 or after a lapse of a predetermined time, the pseudo generated break information of the immediately preceding make information is stored in the queue buffer, and the key is stored in this queue buffer. By extracting the input information and notifying the system that needs the break information, the make information can be converted into make information and break information that does not cause a malfunction.

〔Example〕

Next, the configuration and operation of one embodiment of the present invention will be sequentially described in detail with reference to FIGS. 2 and 3.

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

The keyboard 2 is for a user to input various data by keys. When a key input is made from the keyboard 2, the CPU 1 is notified of this by an interrupt, and the key input information is processed as shown in FIG. 3 described later.

The queue buffer 3 is a buffer for temporarily storing key input information input from the keyboard 2.

The timer 4 is a timer that causes the CPU 1 to generate an interrupt at predetermined intervals and, when break information is stored in the break notification register 5, extracts the break information and stores and clears it in the queue buffer 3 to activate a routine.

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

The CPU6 is a processor that operates in the secondary OS, and when it is desired to use the key input information from the keyboard 2, the CPU6 is notified of this by an interrupt, and the queue buffer 3, CPU1,
Also, the key input information from the keyboard 2 and the pseudo-generated break information are received via the communication register 7.

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 of FIG. 2 will be described in detail using the flow chart of FIG.

FIG. 3A shows a processing flowchart of key input information.

In FIG. 3A, it is determined whether or not break information needs to be generated. This is done by referring to a table (not shown) or the like to determine whether the makeup information keyed in from the keyboard of FIG. 2 is the makeup information of the key for generating the break information. In case of YES (when it is the make information of the key for which the break information is not generated), perform. In the case of NO (when it is the make information of the key for generating the break information), the key input information (key make information, break information, tie matic for the key for generating the break information) key input from the keyboard 2 to the cue buffer is performed. Information), and exit.

Determines whether the break notification register is empty. YE
In the case of S (when the break information pseudo-generated in the break notification register 5 is not stored), the procedure is performed. In the case of NO (when the break information pseudo-generated in the break notification register 5 is stored), the break information stored in the break notification register 5 is stored in the queue buffer 3, and the procedure is performed.

Stores make information in the queue buffer.

Stores the break information in the break notification register. This stores the make information key-input from the keyboard 2 in the queue buffer 3 and then stores the pseudo-generated break information in the break notification register 5.

As described above, the processing for the key input information is performed.

Next, FIG. 3B shows a processing flowchart by the interrupt routine.

In FIG. 3B, the timer interrupts the CPU1.

Determines whether it is time out. In the case of YES (after storing the break information pseudo-generated in FIG. 3B) in the break notification register 5, for example, 20 ms to 500 m
If it exceeds s), perform. If NO, repeat.

Determines whether the break notification register is not empty. In the case of YES (when the break information is stored in the break notification register 5), the break information stored in the break notification register 5 is taken out, stored in the queue buffer 3 and cleared, and the processing ends. NO
In the case of (when the break information is not stored in the break notification register 5), the process ends without doing anything.

As described above, when the break information is stored in the break notification register 5 for a predetermined time (about 20 ms to 500 ms), the break information is stored in the queue buffer 3 and cleared. Then, the makeup information, break information, and tiematic information stored in these queue buffers 3 are subordinated.
Notify CPU6 running on the OS.

〔The invention's effect〕

As described above, according to the present invention, the pseudo generated break information of the immediately preceding make information is queued in response to the input of make information of the key that does not generate break information from the keyboard 2 or after a predetermined time has elapsed. The key input information entered by the keyboard 2 used under the Matsuri OS is adopted because it is stored in the buffer 3 and the key input information is extracted from the queue buffer 3 and notified to the system that requires the break information. Among them, the make information can be converted into make information and break information that do not cause a malfunction.

[Brief description of drawings]

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

Claims (1)

[Claims] 1. In a keyboard control method for generating break information based on make information from a keyboard, a queue buffer (3) for storing key input information input from a keyboard (2) and a key input information are stored. A break notification register (5) that stores the break information generated when the make information of the key that does not generate the break information is provided, and corresponds to the notification of the make information of the key that does not generate the break information from the keyboard (2). When the break information is stored in the break notification register (5), the break information is extracted and stored in the queue buffer (3), the make information is stored in the queue buffer (3), and the generated break information is stored in the break information. In addition to storing in the notification register (5), the break notification register (5) is broken after a lapse of a predetermined time. When the information is stored, it is taken out, stored and cleared in the queue buffer (3), the key input information is taken out from the queue buffer (3), and the break information is notified to the system that needs it. A keyboard control method characterized by the above.