Project Auto-Save Fix + ARM macOS Build

This release primarily fixes issue #227, where a recent change to the MakePlayingCards frontend caused the desktop tool's auto-save functionality to no longer work correctly. Please let me know if you encounter any further issues with this feature!

The other changes are in this release:

• When the tool initially loads, the browser will load a landing page instructing you to check the console window for further input - thanks to @coderanger for contributing this in #242!
• Binaries for the desktop tool are now distributed for both kinds of macOS CPU architectures - Intel and ARM (Apple silicon) - resolving #247

I was planning to include a few other changes in this release, but the priority here is getting a fix for #227 into your hands.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.5.1...v4.5.2

Support for Multiple XMLs - Hotfix

This release fixes issue #236, where saving your project while autofilling didn't work correctly and would stop the process. It also adds better logging capability to the tool - if it crashes, it will write out a log file which will help to debug these sorts of issues more quickly in the future.

To recap, the previous release adds functionality for working with multiple XML files in one execution of the tool. It works as follows:

• Multiple XML files can be selected when the tool starts rather than just one.
• The tool will process XMLs together where possible, and it determines whether they can be processed together by their cardstock and surface finish (foil/nonfoil).
  • For example, a 200 card XML and a 300 card XML would be processed as one 500 card order.
• Where combined projects exceed MakePlayingCards' maximum order size of 612 cards, the user will be prompted as to how the card should be split over multiple orders.
  • The tool currently supports the following split methods:
    • Naively splitting every 612 cards,
    • Splitting according to splits specified by the user (e.g. 400 cards in one order and 500 cards in another order).
• This also includes functionality for processing XMLs which individually exceed 612 cards.
  • I'm planning on enhancing the frontend at a later date to allow producing larger XML files than 612 cards.
• The command line argument skipsetup has been moved - the tool will prompt the user about this when commencing work on each order.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.5...v4.5.1

Support for Multiple XMLs

This release adds functionality for working with multiple XML files in one execution of the tool. It works as follows:

• Multiple XML files can be selected when the tool starts rather than just one.
• The tool will process XMLs together where possible, and it determines whether they can be processed together by their cardstock and surface finish (foil/nonfoil).
  • For example, a 200 card XML and a 300 card XML would be processed as one 500 card order.
• Where combined projects exceed MakePlayingCards' maximum order size of 612 cards, the user will be prompted as to how the card should be split over multiple orders.
  • The tool currently supports the following split methods:
    • Naively splitting every 612 cards,
    • Splitting according to splits specified by the user (e.g. 400 cards in one order and 500 cards in another order).
• This also includes functionality for processing XMLs which individually exceed 612 cards.
  • I'm planning on enhancing the frontend at a later date to allow producing larger XML files than 612 cards.
• The command line argument skipsetup has been moved - the tool will prompt the user about this when commencing work on each order.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.4.1...v4.5

S27 Stock Support

Welcome to the new year folks! I'm absolutely over the moon to announce that we surpassed 100,000 total downloads of the desktop tool last week - thank you so much for your ongoing support :)

This minor release includes the following changes:

• The tool now supports creating projects with S27 (smooth) cardstock as requested in #195 .
• #201 identified that different vendors (MakePlayingCards vs PrinterStudio) can have different bracket sizes (e.g. up to 54 cards vs up to 55 cards). The tool now dynamically identifies what brackets your vendor of choice offers when auto-filling your project.
• Some users were confused about how to progress after signing into the tool when prompted to press enter in the console window. The tool will now automatically resume when it detects that you've signed in.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.4...v4.4.1

Auto-Save Project and PrinterStudio Support

This release been in the works for a little while - thanks for your patience! It release includes the following new features:

• The tool will now periodically save your project to your MakePlayingCards (or PrinterStudio) account throughout the upload process. This is intended to minimise time wastage from the scenario where the tool encounters an error halfway through an auto-fill process. It'll auto-save your project by default but you can opt out of this behaviour.
• The tool now supports uploading your project to https://printerstudio.com and https://printerstudio.de - thanks to @lukegothic for the initial contribution here!
  • We can investigate adding support for the other regional variants of https://printerstudio.com - please create a GitHub Issue if that's something you're interested in.

And it includes the following bugfixes:

• There have been several improvements to the stability of the --skipsetup flag - this has been pretty broken for a long time and I apologise for that - please let me know if you continue to encounter issues with it!
• We've made an internal change which fixes Brave support - thanks for your patience with this! I expect there to be fewer random breakages like this on the webdriver front going forward.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.3.2...v4.4

Webdriver Fix Redux

This release is a follow-up to https://github.com/chilli-axe/mpc-autofill/releases/tag/v4.3.1 which contained a buggy version of webdriver_manager. I have picked up the latest version of that library (4.0.0) and tested on macOS, Windows, and Ubuntu, and both Chrome and Edge performed as expected across all platforms.

Note: There appears to be a lingering issue in webdriver_manager which prevents Brave from initialising. I have decided to create this release despite Brave not working to get the Chrome bugfix out to users (since Chrome is the browser most commonly used with the tool). I'll continue to monitor the Brave situation and will create another release when appropriate. I've raised the issue with webdriver_manager here: SergeyPirogov/webdriver_manager#579

I have also made a few other changes which:

• Should prevent image-downloading threads from falling over due to uncaught exceptions,
• Provide an escape hatch in case of uncaught exceptions in the browser automation thread which does not break program flow
  • i.e. if something goes wrong while autofilling your order, the tool should now give you the option to retry or skip that action without dying on the spot.
• Resolve #128 by providing better fallback logic in case the API query to retrieve the project cardback's filename fails (.png is assumed).

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.3.1...v4.3.2

Chrome 115 Webdriver Fix

Update: I'm aware of users encountering webdriver issues on this release due to bugs being present in webdriver_manager==3.9.0. Please use the next release instead (when it's available). Thank you for your patience!

---

This release upgrades our dependency on webdriverSmanager to 3.9.0, which picks up a bugfix for Chrome version 115 and later - the release notes are here: https://github.com/SergeyPirogov/webdriver_manager/releases/tag/v3.9.0. Aside from upgrading this dependency, this release contains no functional changes from the previous one.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.3...v4.3.1

Image Post-Processing

This release incorporates image post-processing into the desktop tool. Downloaded images can be downscaled according to a maximum DPI before being uploaded to MakePlayingCards; the default value is 800 DPI, which should reduce order creation times without sacrificing print quality (as MakePlayingCards prints at 800 DPI at most).

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.2.5...v4.3

Command-Line Improvements and Bug Fixes

This release includes the following new features:

• The tool will now keep your computer awake by default: #131 - thank you to @AitanBachrach for authoring!
• The tool will now prompt you to optionally input values for the most commonly used command-line arguments: #143 - thank you to @AitanBachrach for authoring!
• You can now pass the path to your browser's binary (executable) with --binary-location in case its location is not detected properly

It also contains the following bugfixes:

• The tool would break on rare occasions with the error message unhandled inspector error: ... No node with the given id found: #141
• The Brave browser was not properly identified (Chrome was being opened instead): #142

Please create a GitHub Issue if you continue to encounter either of these problems on this release.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.2.4...v4.2.5

Fix Rare Uncaught Exception When Paging to Fronts

This minor release fixes an issue where the tool would rarely fail to move to the cardfront editing step: #123

Please create a GitHub Issue if you continue to encounter this problem on this release.

Please refer to the instructions here for how to run the application on each platform.

Commits since previous release: v4.2.3...v4.2.4