Same thing, just unresponsive Capture and no CPU pegging.So how did you arrive at that file set? Maybe the technique could help me.-Updated -Actually, cdsMsgServer/NameServer don't appear in the task list unless I include all those files, but Capture still doesn't run. Then I introduced cdsCommon.dll, then the minor dll's. No missing DLL messages or anything like that. This decision is only partly technical, there might be subjective reasons to use one thing or the other.I don't get the CPU pegging, now, and I see cdsMsgServer/NameServer running with a single instance, finally, but Capture still doesn't execute just hangs for about a minute and then gets killed off as 'unresponsive'.I tried just copying over cdsMsgServer/NameServer.exe but I get the same thing. Now do the same for Arial, Verdana, Tahoma. See the fancy lines, the narrow segments, the elegant design? That's not a good choice for a small-dpi, smudge-prone printer. Write something in Times New Roman in very large font.
Use a font that doesn't have fancy strokes that need many pixels to paint OR make smudges more obvious.Or use the font others have spent millions in developing: open your favorite version of Ms Word, type a few words and see what font is used. Invest millions in developing a special purpose font that's easy to read on paper and behaves good printed on whatever device.On today's computers bitmap fonts only serve one purpose: look good at small pixels count. The printer driver is not helping you at all and you end up writing device-specific routines. But it is hard work and you'll be outside of the 'comfort zone'. The device allows font scaling, drawing lines, almost everything you'd need.
The only time I had to deal with a thermal printer I used this method and the results really are great. Results will be outstanding, and there's enough flexibility to also get beautiful results. The device fonts: don't print graphics to tiny printers, use the on-board fonts and learn the 'escape' language.In my opinion the selected font should be, based on priority:
0 kommentar(er)
