I also changed the internal JSON slightly to use "interruptIn" which appears to be closer to the USB terminology, as opposed to "interruptRead" which is a libusb utility function. Ultimately for most users this is transparent as the python printer will still emit interruptRead()
fixes https://github.com/JohnDMcMaster/usbrply/issues/61
I also changed the internal JSON slightly to use "interruptIn" which appears to be closer to the USB terminology, as opposed to "interruptRead" which is a libusb utility function. Ultimately for most users this is transparent as the python printer will still emit interruptRead()