Bert Driehuis
Bert Driehuis
It would be nice if we had a process to build these installers automatically or at least easily, but for now making sure the links point somewhere would be better...
I've done some experimentation with automating the builds using Appveyor and briefcase. It seems the current aboutDialog.py was added after the last Windows build, and it will need some tweaks...
Appveyor spit out a working Windows binary on https://ci.appveyor.com/project/driehuis/trufont-win/build/artifacts. I'll try to get a Linux and Mac pipeline up as well, and once I get those to build I'll open...
The Appveyor builds are not supported builds, but thanks for testing them anyway. I will open a new issue to discuss these builds and would like to propose that, now...
Bumping GlyphCellHeaderHeight to 15 (from 13) resolves the clipping for me.
For whatever it's worth, I had an issue much like this. Systemd's fido_id couldn't access the report descriptor: `fido_id[1051010]: 1-2:1.0: Failed to open report descriptor at '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/report_descriptor': No such file...
I didn't spot this issue when I went over the issue list, but pull request #911 adresses this issue when it comes to the PDF report. @TeoGoddet, what was your...
I'll see if I can remove the -0.01% of code coverage introduced by this patch.
Hmmm, seems like the actual report generation is not tested at all.
Actually generating a report in the test has bumped code coverage for `open_items.py` from 7% to 53%, and ensured that all added code has been tested.