Per Gantelius
Per Gantelius
Probably the same as https://github.com/stuffmatic/fSpy/issues/44
That dependency was specified by Electron, and seems to have [been removed](https://github.com/electron/electron/pull/19498) now. I'll make sure the next fSpy version is based on the most recent Electron version, which should...
Could you describe the workflow you have in mind with a bit more detail?
This only applies to single vanishing point calibration, right? Because when two vanishing points are used, fSpy doesn't need to know the dimensions of the sensor.
There is actually an undocumented command line interface that lets you do just that. You should be able to see supported parameters etc in [the CLI source](https://github.com/stuffmatic/fSpy/blob/develop/src/cli/cli.ts) (especially `printUsage`).
I'm not sure I understand this issue. Some screenshots would be great.
Thanks for the report! What's the resolution of your screen?
I just had a look at [the spec](https://usb.org/sites/default/files/midi10.pdf) and it looks like using `.device_class(USB_CLASS_NONE)` is correct. At the top of page 11, the spec states that _As is the case...
Looking closer at the [command documentation](https://download4.epson.biz/sec_pubs/pos/reference_en/escpos/gs_cv.html), it states for the TM-T20, TM-T20II and TM-T20III that _Only a partial cut (one point left uncut) is available. Therefore the behavior is the...
Update: I tried the checkout flow in a private window and it seems to work, so maybe I've got some stale cookie data or something. Regardless, it would be nice...