|
| Inicio → WINDEV 2024 → Printing "dots" to "Text Only" driver with iprint command goes wrong. |
| Printing "dots" to "Text Only" driver with iprint command goes wrong. |
| Iniciado por m.bouman, 19,dic. 2017 15:23 - 2 respuestas |
| |
| | | |
|
| |
| Publicado el 19,diciembre 2017 - 15:23 |
Good afternoon,
When we try to print the decimal point, ascii code 46, to a generic text only driver with the iPrint command, the result is that after printing the point, the printer does not move forward for printing the next character. It prints the next character on top of the dot.
Anyone else noticed this, or knows if this is a bug? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 19,diciembre 2017 - 16:14 |
Martijn Bouman wrote:
Good afternoon,
When we try to print the decimal point, ascii code 46, to a generic text only driver with the iPrint command, the result is that after printing the point, the printer does not move forward for printing the next character. It prints the next character on top of the dot.
Anyone else noticed this, or knows if this is a bug?
I have an addition, which makes it even worse. When you print the "point" it keeps sending an CR command, and then prints the number of spaces it should go, to get back to the location of the point.
When we use iPrint("6.01.03.009") and check with Wireshark to see what gets transferred to the printer the HEX codes are as follows.
36 30 0d 20 2e 31 2e 0d 20 20 20 30 33 30 0d 20 20 20 20 20 2e 30 39
This translates in ASCII to 60. .1.. 030. .09 Where the dots are actually <CR> commands instead of "Points"
This messes up the printing of the dots. |
| |
| |
| | | |
|
| | |
| |
| Publicado el 22,enero 2018 - 16:30 |
I have the same problem ?
Have you find a solution ? |
| |
| |
| | | |
|
| | | | |
| | |
|