Hello, > Ok, and what's the problem? That the server wants to print to the > printer? That the application sends data to the "screen" (a terminal > emulator) instead of sending it to the printer? That it is necessary > to see the printer data displayed in a terminal emulator?
The problem here revolves around the interaction between the terminal emulator, the application, and the printing process. The terminal emulator has a "printing passthrough" function, which means that depending on the user's interactions with the application, data can be displayed on the screen and, at times, passed through the terminal's passthrough mode to be printed on the physical printer. So, to address your questions specifically: 1. The server itself doesn't initiate printing; instead, it's the user on the workstation with the terminal emulator who wishes to print to their local printer. The application running on the server sends data to the user's screen (terminal emulator) and, when requested by the user, can be sent to the user's local physical printer connected to their workstation. 2. The application may send data to both the screen and the printer, depending on the specific user interactions and transaction requirements. The screen serves as a visual interface for the user, while the printer captures some of the data for hardcopy records. 3. It's necessary to have the option to selectively send certain data to the physical printer from the terminal emulator based on the user's choice, as it provides real-time feedback and visibility for the user during interactions with the application. However, not all data displayed on the screen needs to be sent to the printer, as it may include additional information or layout formatting relevant to the current screen content or user interactions. The display on the screen and the printing on the printer are designed to complement each other based on the specific transactional needs and the user's preferences. Regards, Thierry
