JP2012213859A - Printer, program, and printer system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a printer, a program, and a printer system, for easily transmitting data to applications provided in a computer.SOLUTION: The printer includes: a plurality of end points (EP0 to EPx) to be used for communication with the computer 10; and a CPU 42 configured to interrupt-transfer a keycode to the computer 10 from at least one end point EP2 to be used for HID (Human interface Device)-class communication among the plurality of endpoints (EP0 to EPx).

Description

  The present invention relates to a printer, a program, and a printer system.

  In many cases, a universal serial bus (USB) is used as a connection interface between a computer and various computer peripheral devices such as a keyboard, a mouse, and a printer. The USB is designed in consideration of ease of use by the user, such as a plug and play function related to computer peripheral devices and a common connector cable.

  Between the computer and the printer, print data is communicated from the computer to the printer, and for example, printer status data is communicated from the printer to the computer. Patent Document 1 discloses a technique for interrupt-transferring free state data in a data storage area of a printer to a computer. Japanese Patent Application Laid-Open No. H10-228688 discloses a technique for adding product attribute data to a get descriptor from a computer followed by data such as a product name and transmitting the data. Japanese Patent Application Laid-Open No. 2004-228561 discloses a technique for bulk transferring printer status data from a digital printer to a digital camera.

JP 2002-318778 A JP 2004-272570 A JP 2005-31080 A

  When the computer and the printer are connected via the USB interface, bulk transfer is generally used for communication between the computer and the printer. That is, when transferring printer status data from a printer to a computer, for example, bulk transfer is used. The printer status data transmitted to the computer is finally notified to a predetermined application (for example, a printing application) of the computer.

  However, for example, when trying to notify the printer application of printer status data, complicated processing is required. Therefore, the present invention has been made in view of such a problem, and an object of the present invention is to provide a printer, a program, and a printer system capable of easily notifying data to an application.

  The present invention includes a plurality of endpoints used for communication with a computer, and a control unit that interrupt-transfers a key code to the computer from at least one of the plurality of endpoints used for HID class communication; A printer comprising: According to the present invention, data can be easily notified to an application provided in a computer without using a device driver or software that performs complicated processing.

  In the above configuration, the key code may be a key code corresponding to a printer status.

  In the above configuration, the storage unit stores the key code, and the control unit interrupt-transfers the key code stored in the storage unit to the computer and also stores the storage based on an instruction from the computer. The key code stored in the section can be changed. According to this configuration, it is possible to set a key code according to the usage situation for each user.

  The present invention relates to a computer connected to a printer having a plurality of endpoints, wherein a key code is interrupt-transferred from at least one endpoint used for HID class communication among the plurality of endpoints. Acquisition means for acquiring the key code before the active application is notified to the active application as a keyboard event, and the key code acquired by the acquisition means is stored in the storage unit A program for causing a conversion means for converting into a window message corresponding to a code, and a notification means for notifying an application stored as a notification destination in the storage section of the window message converted by the conversion means. is there. According to the present invention, data transmitted from a printer can be notified not only to an active application but also to an arbitrary application.

  In the above configuration, the key code may be a key code corresponding to a printer status.

  The said structure WHEREIN: The said conversion means can be set as the structure which converts the said key code acquired by the said acquisition means into the keyboard event corresponding to the said key code.

  The said structure WHEREIN: It can be set as the structure which has a 1st change means to change the said application of the notification destination memorize | stored in the said memory | storage part.

  The said structure WHEREIN: It can be set as the structure which has the 2nd change means to change the said window message memorize | stored in the said memory | storage part.

  The present invention relates to a printer for interrupt-transferring a key code corresponding to a printer status from at least one endpoint used for HID class communication among a plurality of endpoints used for communication between the computer and the computer to the computer. A printer system comprising: According to the present invention, data can be easily notified to an application provided in a computer without using a device driver or software that performs complicated processing.

  In the above configuration, the computer acquires the key code before the active application is notified as a keyboard event of the key code interrupt-transferred from the one endpoint, and the key code is stored in the storage unit. The window message may be converted into a window message corresponding to the key code, and the window message may be notified to an application stored as a notification destination in the storage unit. According to this configuration, the data transmitted from the printer can be notified not only to the active application but also to an arbitrary application.

  According to the present invention, data can be easily notified to an application provided in a computer without using a device driver or software that performs complicated processing.

FIG. 1 is an example of a functional block diagram of a printer system according to the first comparative example. FIG. 2 is an example of a block diagram illustrating the overall configuration of the printer system according to the first embodiment. FIG. 3 is an example of a functional block diagram of the printer system according to the first embodiment. FIG. 4 is an example of a sequence diagram illustrating a control transfer communication procedure between a computer and a printer. FIG. 5 is an example of the descriptor (part 1). FIG. 6 shows an example of the descriptor (part 2). FIG. 7 is an example of a flowchart for transmitting a key code corresponding to the printer status. FIG. 8 is an example of a USB key code, an actual key, and a Windows (registered trademark) virtual key code corresponding to the printer status. FIGS. 9A and 9B are examples of packet data transmitted from the printer when notifying the printer status. FIG. 10 is an example of a flowchart for explaining printer status determination processing in a print application. FIG. 11 is an example of a block diagram illustrating the overall configuration of the printer system according to the second embodiment. FIG. 12 is an example of a functional block diagram of the printer system according to the second embodiment. FIG. 13 is an example of a flowchart for explaining a control process performed by the resident application. FIG. 14 is an example of a flowchart for explaining the processing of the key code hook routine in the resident application. FIG. 15 is an example of a flowchart for explaining processing for changing the contents stored in the storage unit by the resident application.

  First, the problem to be solved by the present invention will be described in detail using the printer system according to Comparative Example 1. FIG. 1 is an example of a functional block diagram illustrating a printer system according to the first comparative example. As shown in FIG. 1, in the printer system 300, a computer 70 and a printer 80 are connected via a USB interface. The computer 70 includes a printing application 12, a GDI (Graphics Device Interface) 14, a printer driver 16, a spooler 18, a language monitor 20, a port monitor 22, a USB bulk driver 24, a USB driver stack 26, a USB host controller 28, and a driver API ( Application Programming Interface) 72. The driver API 72 is a dedicated application for notifying the printer application 12 of printer status data of the printer 80. The USB bulk driver 24 is a printer driver used for communication with the printer 80, and the USB driver stack 26 is a Windows (registered trademark) operating system of Microsoft (registered trademark) for operating the USB host controller 28. It is a driver. The USB host controller 28 is provided in the interface of the computer 70 and manages communication with the printer 80.

  The interface of the printer 80 is provided with a plurality of end points (EP0 to EPx). The end point EP0 is used for control transfer. The end point EP1 is an end point for receiving print data, and is used for OUT one-way bulk transfer as seen from the computer 70. The endpoint EP2 is an endpoint for transmitting printer status data, for example, and is used for one-way bulk transfer of IN as viewed from the computer 70.

  The printer status data bulk-transferred from the end point EP2 is passed to the spooler 18 via the USB host controller 28, the USB driver stack 26, the USB bulk driver 24, the port monitor 22, and the language monitor 20. For example, the following four methods are conceivable as methods for notifying the printer application 12 of such printer status data.

  The first notification method is that the language monitor 20 communicates with the port monitor 22, constantly monitors the data transmitted from the printer 80, and notifies the print application 12 via the driver API 72 when printer status data is acquired. It is a method to do.

  The second notification method is a method in which the driver API 72 communicates with the USB bulk driver 24 to constantly monitor data transmitted from the printer 80 and notify the print application 12 when printer status data is acquired.

  The third notification method is a method in which the print application 12 communicates with the USB bulk driver 24, directly monitors data from the printer 80, and acquires printer status data.

  In the fourth notification method, the USB bulk driver 24 communicates with the USB driver stack 26, constantly monitors data from the printer 80, and acquires printer status data via the driver API 72 or directly with the printing application 12. It is a method to notify.

  In any of these four notification methods, an application, a driver, or the like must periodically communicate to read printer status data. In some cases, a driver API 72, which is a dedicated application for notifying the printer status data to the print application 12, may be used. Thus, complicated processing is required to notify the printer status data to the printing application. Therefore, in order to solve such a problem, an embodiment capable of easily notifying data to an application will be described below.

  FIG. 2 is an example of a block diagram illustrating the overall configuration of the printer system according to the first embodiment. As shown in FIG. 2, in the printer system 100 according to the first embodiment, the computer 10 and the printer 40 are connected via a USB interface cable 52. The computer 10 includes a CPU 30, a memory 32 including a ROM and a RAM, and an I / F (interface) 34. The CPU 30 controls the entire computer 10 according to a control program stored in the memory 32. The I / F 34 is an interface that connects the computer 10 and the printer 40.

  The printer 40 includes a CPU 42, a memory 44 including a ROM and a RAM, an I / F 46, a storage unit 48 including a flash ROM, and a printing unit 50. The CPU 42 controls the entire printer 40 according to a control program stored in the memory 44. The I / F 46 is an interface that connects the printer 40 and the computer 10. The I / F 46 is provided with a plurality of end points as will be described later. The storage unit 48 stores a key code associated with the printer status. The print unit 50 executes printing based on the print data sent from the computer 10.

  FIG. 3 is an example of a functional block diagram of the printer system according to the first embodiment. As shown in FIG. 3, the computer 10 includes a print application 12, a GDI (Graphics Device Interface) 14, a printer driver 16, a spooler 18, a language monitor 20, a port monitor 22, a user interface 23, a USB bulk driver 24, an HID (Human Interface). Device) driver 25 and USB driver stack 26 are provided. The I / F 34 includes a USB host controller 28 that manages communication with the printer 40.

  The print application 12, GDI 14, printer driver 16, spooler 18, language monitor 20, port monitor 22, and user interface 23 are provided in the user mode. The USB bulk driver 24, the HID driver 25, and the USB driver stack 26 are provided in the kernel mode. The USB bulk driver 24 provided in the kernel mode is a printer driver used for communication with the printer 40. The HID driver 25 is a keyboard driver used for communication with the printer 40. The USB driver stack 26 is a driver for operating the USB host controller 28 in the Windows (registered trademark) operating system of Microsoft (registered trademark).

  The I / F 46 included in the printer 40 is provided with a plurality of end points (EP0 to EPx). The end point EP0 is used for control transfer. Configuration is performed using this control transfer, and setting information on how to use the printer 40 is bidirectionally communicated between the computer 10 and the printer 40. The end point EP1 is an end point for receiving print data. The end point EP1 is one-way communication OUT as seen from the computer 10. Bulk transfer is used as the transfer method. The end point EP2 is an end point for transmitting a key code corresponding to the printer status, and is one-way communication IN as viewed from the computer 10. Interrupt transfer is used as the transfer method.

  Here, a communication procedure of control transfer between the computer 10 and the printer 40 will be described with reference to the sequence diagram of FIG. As shown in FIG. 4, when the printer 40 is turned on with the computer 10 and the printer 40 connected (step S10), the computer 10 confirms that the printer 40 is turned on. After (step S12), the get descriptor is transferred to the printer 40 (step S14). Note that steps S10 and S12 may be performed when the printer 40 in the power-on state is connected. In response to the get descriptor, the printer 40 returns the descriptor information stored in the memory 44 to the computer 10 (step S16). The computer 10 makes settings such as preparing an appropriate driver based on the returned descriptor information (step S18).

  5 and 6 show examples of descriptor information stored in the memory 44. FIG. In the example of descriptor information shown in FIGS. 5 and 6, the printer class and bulk transfer are specified by the interface 1 descriptor and the endpoint 1 descriptor. The HID keyboard class and interrupt transfer are specified by the interface 2 descriptor and the endpoint 2 descriptor. As a result, the computer 10 recognizes the printer 40 as two devices, a printer and a keyboard, and prepares the USB bulk driver 24 as a driver for the printer as described with reference to FIGS. 2 and 4. HID driver 25 is prepared as follows.

  Since the printer class and the bulk transfer are specified by the interface 1 descriptor and the endpoint 1 descriptor, the endpoint EP1 is used as an endpoint for receiving the bulk-transferred print data. On the other hand, since the HID keyboard class and the interrupt transfer are specified by the interface 2 descriptor and the endpoint 2 descriptor, the endpoint EP2 is an endpoint for transmitting the key code corresponding to the printer status by the interrupt transfer. used.

  Here, the printing process until printing is performed by the printing unit 50 of the printer 40 when the printing process is started by the printing application 12 will be described. As shown in FIG. 3, when the printing process is started by the printing application 12, the printing application 12 calls the GDI 14, and the GDI 14 performs drawing on the printer device context. Thereafter, the GDI 14 calls the printer driver 16, and the printer driver 16 generates print data that can be printed by the printer 40 based on the printer language. The generated print data is passed to the spooler 18.

  Next, if necessary, the language monitor 20 performs processing, and then the port monitor 22 performs print data output processing in accordance with the type of printer port. The print data is notified to the USB bulk driver 24 and the USB driver stack 26 provided in the kernel mode, and then transmitted to the printer 40 by bulk transfer under the management of the USB host controller 28.

  After receiving the bulk transfer print data at the end point EP1 of the printer 40, printing is executed by the printing unit 50 based on the print data under the control of the CPU.

  FIG. 7 is a flowchart illustrating transmission of a key code corresponding to the printer status. As shown in FIG. 7, the CPU 42 of the printer 40 determines whether or not an abnormality has occurred in the printer status and there is a printer status to be notified to the computer 10 (step S20). If it is determined that there is a printer status to be notified, the CPU 42 obtains a key code corresponding to the printer status to be notified from the endpoint EP2 based on the key code associated with the printer status stored in the storage unit 48. It transmits to the computer 10 (step S22). When determining that there is no printer status to be notified, the CPU 42 transmits a NAK from the end point EP2 to the computer 10 (step S24). The transfer method at the end point EP2 is interrupt transfer, and the interrupt transfer operation causes an IN transaction at an interval [ms] specified by EP_bInterval of the end point 2 descriptor. That is, the CPU 42 transmits a key code or NAK corresponding to the printer status to the IN transaction.

  Returning to FIG. 3, the key code corresponding to the printer status transmitted from the endpoint EP2 is sent to Windows (registered trademark) via the USB host controller 28, the USB driver stack 26, and the HID driver 25 which is a keyboard driver. The user interface 23 provided as a standard is notified. The key code is converted into a keyboard event (WM_KEYDOWN / WM_KEYUP window message and virtual key code) by the user interface 23 and notified to the print application 12 as a keyboard event.

  Here, FIG. 8 shows an example of a USB key code associated with the printer status, an example of an actual key corresponding to each USB key code, and an example of a Windows (registered trademark) virtual key code. As shown in FIG. 8, examples of printer status include no paper, near end, mark not detected, cover open, cutter error, hardware error, power supply voltage error, head temperature error, etc. 6A to 6F, 70 and 71 are assigned. The USB key codes 6A to 6F, 70, and 71 correspond to F15 to F22 in actual keys, and when converted to Windows (registered trademark) virtual key codes by the user interface 23, for example, the USB key code 6A is converted to Windows (registered). Trademark) virtual key code 7E (VK_F15).

  The reason for assigning 6A to 6F, 70, 71 as the USB key codes associated with the printer status is that the actual keys F15 to F22 corresponding to the USB key codes 6A to 6F, 70, 71 are generally This is because the key is not used. Therefore, the USB key code assigned to the association with the printer status is not limited to 6A to 6F, 70, 71, but it is preferable to assign a USB key code corresponding to a key that is not normally used.

  FIGS. 9A and 9B are examples of packet data transmitted from the printer 40 when the printer status is notified. FIG. 9A shows an example of packet data when the printer status without paper is generated and when the printer status is canceled. FIG. 9B shows an example of packet data when the printer status with cover open and no paper is generated at the same time, when the printer status with cover open is canceled, or when the printer status with cover open and paper is released. It is. The number of packet data is determined by the number of bytes specified by EP_wMaxPacketSize of the endpoint 2 descriptor (8 bytes in the first embodiment), and key codes corresponding to the printer status are stored in order from the third byte. Therefore, when the printer status without paper in FIG. 9A occurs, the key code 0x6A without paper is stored in the third byte. When the printer status without cover open and no paper in FIG. 9B occurs, the key code 0x6D for cover open is stored in the third byte, and the key code 0x6A without paper is stored in the fourth byte.

  9A is transmitted from the printer 40 and when the key code is notified to the user interface 23, the key code 0x6A is converted into a keyboard event by the user interface 23, and finally. The print application 12 is notified of the keyboard event of WM_KEYDOWN and the virtual key code 7E (VK_F15). Similarly, in the case of packet data at the time of cover open and no paper occurrence shown in FIG. 9B, the keyboard event of WM_KEYDOWN and virtual key code 81 (VK_F18), 7E (VK_F15) is notified to the printing application 12. .

  Also, as shown in FIG. 9A, when the printer status without paper is released, packet data with 0x6A cleared is transmitted from the printer 40, and a keyboard event of WM_KEYUP and virtual key code 7E (VK_F15) is printed. The application 12 is notified. As shown in FIG. 9B, when only the cover open printer status is canceled, 0x6D is cleared, packet data in which 0x6A is stored in the third byte is transmitted, and WM_KEYUP and virtual key code 81 ( VK_F18) is notified to the print application 12. Thereafter, when the printer status without paper is canceled, packet data with 0x6A cleared is transmitted, and the keyboard event of WM_KEYUP and virtual key code 7E (VK_F15) is notified to the printing application 12.

  Next, a printer status determination process performed by the print application 12 when a keyboard event is notified will be described. FIG. 10 is an example of a flowchart for explaining printer status determination processing in the print application 12. As shown in FIG. 10, when receiving the window message (step S30), the print application 12 determines whether the window message is WM_KEYDOWN (step S32). If it is WM_KEYDOWN (in the case of Yes), the print application 12 determines whether the virtual key code is any one of 7E (VK_F15) to 85 (VK_F22) (step S34). If Yes in step S34, the print application 12 generates a printer status corresponding to the virtual key code (step S36). If No in step S34, the print application 12 executes processing according to the window message (step S38).

  If No in step S32, the print application 12 determines whether the window message is WM_KEYUP (step S40). If it is WM_KEYUP (in the case of Yes), the print application 12 determines whether the virtual key code is any one of 7E (VK_F15) to 85 (VK_F22) (step S42). If Yes in step S42, the print application 12 cancels the printer status corresponding to the virtual key code (step S44).

  In the case of No in step S42 and in the case of No in step S40, the print application 12 executes processing according to the window message (step S38).

  As described above, according to the first embodiment, the printer 40 uses one end point EP2 of the plurality of end points EP0 to EPx for communication of the HID class, and assigns a key code corresponding to the printer status. Interrupt transfer. Accordingly, the computer 10 can convert the key code transmitted at a constant cycle by the interrupt transfer into a keyboard event by using the standard HID driver 25 and the user interface 23 in Windows (registered trademark). Can be notified to the print application 12 as a keyboard event. For this reason, the printer application 12 can be easily notified of data relating to the printer status by using the HDI driver 25 and the user interface 23 that are standard on Windows (registered trademark) without using a device driver or software that performs complicated processing. .

  It is preferable that the printer 40 can change the key code associated with the printer status stored in the storage unit 48 based on an instruction such as a printer command or a vendor request from the computer 10. Thereby, for example, a key code that is not normally used can be used as a key code corresponding to the printer status in accordance with the usage status of each user. Further, it is preferable that the key code associated with the printer status is changed while maintaining consistency with the printer status determination process in the printing application.

  In the first embodiment, the key code interrupt-transferred from the end point EP2 used for HID class communication is a key code corresponding to the printer status. However, the present invention is not limited to this. As long as the data is transmitted from the printer 40 to the computer 10, the key code may correspond to items other than the printer status. Further, the end point EP1 and the end point EP2 may be used in a manner opposite to that in the first embodiment. That is, the end point EP1 may be used as an end point that transmits a key code corresponding to the printer status by interrupt transfer, and the end point EP2 may be used as an end point that receives print data transmitted by bulk transfer. . Further, two or more endpoints for transmitting the key code corresponding to the printer status by interrupt transfer may be provided. That is, it is only necessary to use at least one of the plurality of endpoints for HID class communication and to interrupt-transfer the key code corresponding to the printer status.

  In the first embodiment, the computer 10 includes a Windows (registered trademark) operating system. However, the key code transmitted from the printer 40 is converted into a keyboard event and notified to the print application 12. Other operating systems may be provided as long as they have the function. Further, the case where the key code corresponding to the printer status transmitted from the printer 40 is a USB key code is shown as an example. However, a key code other than the USB key code can be used as long as the assigned key can be identified. May be.

  In the printer system 100 according to the first embodiment, a keyboard event is generated on the user interface 23 based on a key code corresponding to the printer status, and the keyboard event is notified to the print application 12. For this reason, the keyboard event is notified only to the active application. Therefore, in the second embodiment, an example in which data relating to the printer status can be notified to an arbitrary application such as an inactive application will be described.

  FIG. 11 is an example of a block diagram illustrating the overall configuration of the printer system according to the second embodiment. As shown in FIG. 11, the printer system 200 according to the second embodiment is related to the first embodiment in that the computer 60 connected to the printer 40 with the USB interface cable 52 includes a storage unit 62 that is a hard disk, for example. Different from the printer system 100. The storage unit 62 is, for example, a registry, and the storage unit 62 stores window information associated with the key code and window information (window name and window class name) or window handle of a notification destination application that notifies the window message. It is remembered. The other configuration is the same as that of the first embodiment and is shown in FIG.

  FIG. 12 is an example of a functional block diagram of the printer system according to the second embodiment. As shown in FIG. 12, the computer 60 is configured by adding a first application 64, a second application 66, and a resident application 68 to the functional blocks of the computer 10 shown in FIG. The first application 64 and the second application 66 are dedicated applications for monitoring the printing application other than the printing application 12 and the printer 40.

  The Windows (registered trademark) operating system has a Win32 API function of SetWindows (registered trademark) HookEx (). By specifying WH_KEYBOARD (0x00000002) as the first argument, the key code transmitted from the printer 40 is obtained. You can hook and get the key code before the keyboard event occurs. Therefore, the resident application 68 performs a key code hook using SetWindows (registered trademark) HookEx, and acquires the key code before the key code transmitted from the printer 40 is notified to the active application as a keyboard event. And based on the window message matched with the key code memorize | stored in the memory | storage part 62, after converting the acquired key code into a window message, the notification destination application (for example, the window message is memorize | stored in the memory | storage part 62, for example) Any one of the printing application 12, the first application 64, and the second application 66 or a plurality of selected applications) is transmitted by PostMessage (). Other configurations are the same as those of the first embodiment and are shown in FIG.

  Next, a control process performed by the resident application 68 when a key code corresponding to the printer status is transmitted from the printer 40 will be described using the flowchart of FIG. As shown in FIG. 13, the resident application 68 first obtains window information or a window handle of a notification destination application from the storage unit 62 after being started (step S50). Subsequently, the resident application 68 acquires a window message associated with the key code from the storage unit 62 (step S52). In the second embodiment, a case where a key code corresponding to a printer status is converted into a WM_KEYDOWN / WM_KEYUP window message will be described as an example. That is, the case where the key code corresponding to the printer status is converted into a keyboard event as in the first embodiment will be described as an example.

  Next, the resident application 68 registers a key code hook routine (step S54). As described above, this is performed by specifying WH_KEYBOARD (0x00000002) as the first argument of SetWindows (registered trademark) HookEx (). By registering the key code hook routine, the resident application 68 can obtain the key code before the key code is notified to the active application as a keyboard event. That is, for example, when the key code corresponding to the printer status is transmitted from the printer 40, the resident application 68 acquires the key code corresponding to the printer status before the keyboard event occurs in the user interface 23 (step S56).

  Next, the resident application 68 converts the key code acquired in step S56 into a window message based on the window message associated with the key code acquired in step S52 (step S58). In the second embodiment, the key code corresponding to the printer status is converted into a WM_KEYDOWN / WM_KEYUP window message and a virtual key code.

  Next, the resident application 68 determines whether the window message is WM_DESTROY (step S60). If it is determined that the window message is not WM_DESTROY (in the case of No), each window message is processed (step S62). In step S62, window messages other than WM_KEYDOWN / WM_KEYUP are processed. When it is determined in step S60 that the window message is WM_DESTROY (in the case of Yes), the resident application 68 deletes the key code hook routine by using UnoWindows (registered trademark) HookEx () (step S64).

  Here, the processing of the key code hook routine in the resident application 68 will be described in detail using the flowchart of FIG. As shown in FIG. 14, the resident application 68 determines whether or not the key is down from the key ON / OFF information received together with the key code (step S70). If it is determined that the key is down (in the case of Yes), the resident application 68 determines whether the virtual key code is 7E (VK_F15) to 85 (VK_F22) (step S72). In the case of Yes in step S72, the resident application 68 searches for the window of the notification destination application acquired in step S50 (step S74). If there is a window (in the case of Yes in step S76), the resident application 68 sets the notification destination application. A keyboard event is notified and a printer status is generated in the window (step S78).

  In the case of No in step S70, the resident application 68 determines whether or not the key is up (step S80). When it is determined that the key is up (in the case of Yes), the resident application 68 determines whether the virtual key code is 7E (VK_F15) to 85 (VK_F22) (step S82). In the case of Yes in step S82, the resident application 68 searches for the window of the notification destination application acquired in step S50 (step S84). If there is a window (in the case of Yes in step S86), the resident application 68 sets the notification destination application. A keyboard event is notified, and the printer status of the window is canceled (step S88).

  In the case of No in step S80, or after executing step S78 and step S88, the resident application 68 passes the processing to the key code hook routine registered by another application or the like by CallNextHookEx () (step S90).

  Next, processing for changing the contents stored in the storage unit 62 by the resident application 68 will be described using the flowchart of FIG. As shown in FIG. 15, the resident application 68 determines whether or not the command input from the user is to change the notification destination application stored in the storage unit 62 (step S100). When the notification destination application is to be changed (in the case of Yes), the resident application 68 changes the notification destination application stored in the storage unit 62 based on a command input by the user (step S102).

  Next, the resident application 68 determines whether or not the command input from the user is to change the window message associated with the key code stored in the storage unit 62 (step S104). When the window message is to be changed (in the case of Yes), the resident application 68 changes the window message associated with the key code stored in the storage unit 62 based on a command input from the user (step). S106).

  As described above, according to the second embodiment, the resident application 68 acquires the key code corresponding to the printer status before the key code corresponding to the printer status is notified to the active application as a keyboard event. . The resident application 68 converts the acquired key code into a window message based on the window message associated with the key code stored in the storage unit 62, and the notification stored in the storage unit 62 of the converted window message. Notify the destination application. By such control, data relating to the printer status can be notified not only to an active application but also to an arbitrary application.

  In the second embodiment, the case where the resident application 68 converts the key code corresponding to the printer status into a keyboard event (WM_KEYDOWN / WM_KEYUP window message and virtual key code) is described as an example, but the present invention is not limited thereto. The resident application 68 may be converted into an arbitrary window message based on the window message associated with the key code stored in the storage unit 62.

  Further, the window message may be notified to one application, or may be simultaneously notified to a plurality of applications. That is, the storage unit 62 may store one application or a plurality of applications as notification destination applications. In addition, a plurality of applications may be stored in the storage unit 62, and a notification destination application may be selected from them.

  As described with reference to FIG. 15, it is preferable that the resident application 68 can change the window message associated with the window message notification destination application and key code stored in the storage unit 62. Note that the change of the notification destination application and the change of the window message associated with the key code are not limited to being performed by the resident application 68, but may be performed by, for example, the print application 12, the first application 64, or the second application 66. Good.

  In the second embodiment, the case where the computer 10 includes a Windows (registered trademark) operating system has been described as an example. However, a key code hook that acquires a key code transmitted from the printer 40 before the occurrence of a keyboard event is possible. Any other operating system may be used. In the second embodiment, the key code hook is used as a method for acquiring the key code from the printer 40, but other methods may be used as long as the key code can be acquired before the keyboard event occurs.

  In addition, this invention is not limited to the Example mentioned above, In the range which does not deviate from the summary, it can change and implement variously.

10 Computer 12 Printing Application 14 GDI
16 Printer Driver 18 Spooler 20 Language Monitor 22 Port Monitor 23 User Interface 24 USB Bulk Driver 25 HID Driver 26 USB Driver Stack 28 USB Host Controller 30 CPU
32 memory 34 I / F
40 Printer 42 CPU
44 Memory 46 I / F
48 Storage Unit 50 Print Unit 52 USB Interface Cable 60 Computer 62 Storage Unit 64 First Application 66 Second Application 68 Resident Application 100 Printer System 200 Printer System EP0 to EPx Endpoint

Claims (10)

Multiple endpoints used to communicate with the computer;
And a control unit that interrupt-transfers a key code from at least one of the plurality of endpoints used for HID class communication to the computer.   The printer according to claim 1, wherein the key code is a key code corresponding to a printer status. A storage unit for storing the key code;
The control unit interrupt-transfers the key code stored in the storage unit to the computer, and changes the key code stored in the storage unit based on an instruction from the computer. The printer according to claim 1 or 2. A computer connected to a printer having a plurality of endpoints and having a key code interrupted from at least one of the plurality of endpoints used for HID class communication;
An acquisition means for acquiring the key code before the active application is notified as a keyboard event of the key code interrupt-transferred from the one endpoint;
Conversion means for converting the key code acquired by the acquisition means into a window message corresponding to the key code stored in a storage unit;
A program which causes the window message converted by the conversion means to function as notification means for notifying an application stored as a notification destination in the storage unit.   5. The program according to claim 4, wherein the key code is a key code corresponding to a printer status.   6. The program according to claim 4, wherein the conversion unit converts the key code acquired by the acquisition unit into a keyboard event corresponding to the key code.   The program according to any one of claims 4 to 6, further comprising first changing means for changing the notification destination application stored in the storage unit.   The program according to any one of claims 4 to 7, further comprising second changing means for changing the window message stored in the storage unit. A computer,
A printer that interrupt-transfers to the computer a key code corresponding to a printer status from at least one endpoint used for HID class communication among a plurality of endpoints used for communication with the computer. Printer system.   The computer acquires the key code before the active application is notified as a keyboard event of the key code interrupt-transferred from the one endpoint, and the key code is stored in the storage unit. 10. The printer system according to claim 9, wherein the window message is converted to a window message corresponding to the message, and the window message is notified to an application stored in the storage unit as a notification destination.

Images