Quote:
Originally Posted by rkomar
It sounds like they left some debugging statement in their keyboard code that writes to standard output. Until they fix that, it looks like some kind of workaround will be required. Thanks for pointing this out and sharing your solution.
|
Do you think there's a way of clearing stdout between calling the keyboard function (which I assume generates the debugging statement) and writing what is captured by it?