Done

• Design an import dialog
• Open it when dropping images
• Open it via a menu entry
• Add additional images via a dialog option
• Edit card properties and copies count
• Edit custom cards in the page card table view
• Editing custom cards in the document does not trigger a re-draw in the document renderer, because the pixmap does not change
• A custom card registry holding a reference to all created custom cards during the application runtime
  • Can be a static CardDatabase class attribute
• Obtain the registered custom card when the user adds additional copies via the import wizard
  • When the user does this, and edits the card via the CardListTable in the dialog, propagate changes to the copies already in the document.

Fix for saving/loading, keeping image quality

• The file hash was based on the scaled QPixmap PNG encoding. This may be unstable. (DONE. Hash is now based on the untouched source image bytes)
• The save file should save the original file unmodified, so that different sizes can be derived without progressing generational quality losses. Scaling must be done at image load time (DONE)
• The file hash alone is insufficient as a key. Needs a composite key including the card size (POINT OBSOLETE)
  • Image size is no longer part of the CustomCard data. It can be used to create cards of arbitrary size. Actual size depends on the page the card is on. (DONE)

Fix idea

• Create CustomCard class, implementing the Card API (DONE)
• Holds the original pixmap in a private attribute (DONE)
  • Uses a cached property to return the pixmap scaled according the the size setting (DONE)
• Remove the is_oversized flag from the CustomCardData table (DONE)
• Use the size hint in Page to create custom cards of appropriate size (DONE)

Not done yet

• Implement tests for all item editor delegates
• Implement switching card size between regular and oversized

Editing card size needs more work

• Handling this is needed:
  • User adds a custom card as regular size
  • Adds the same card image again, this time as oversized
  • User edits the card size from regular to oversized, or vice versa
  • This should merge both cards
• The custom card registry needs to update the map key from custom_card_id to tuple(custom_card_id, card_size)
• Switching card sizes very likely creates a mixed page, so editing the size requires moving cards around
• Maybe ask via a message box "Edit all instances? [Yes/No]"
• Switching card size should use a new instance, because the pixmap is fixed to the current size.

Stretch goals

• DFC check card generation
  • Link front sides with back sides so that a reference to the other side is available
  • CheckCard needs property setters for all editable columns
  • Editing a custom card should update the check card