Card grid for desktop reveal and single-pick dialogs#10646
Card grid for desktop reveal and single-pick dialogs#10646MostCromulent wants to merge 1 commit into
Conversation
Replace the text-list dialogs that desktop matches use for reveal and single-card pick prompts (opponent reveals their hand, look at top N of library, choose a card from a list) with a thumbnail grid. Cards are visual objects; players recognise them by art faster than by name. Dispatch lives inline in ListChooser: when the list is CardView-only and maxChoices <= 1, build a CardImageGrid; otherwise the existing text path runs unchanged. CardImageGrid is genericized over the item type with a small per-type adapter for image-key and footer-text resolution, so the deck-editor art picker continues to use it for PaperCards while in-game dialogs use it for CardViews. Multi-card prompts continue to route through DualListBox. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
doesn't really convince me: and the way it looks right now usability worsens without: If anything that Inquisition of Kozilek could instead let you pick from the players hand view directly (which would also align more with other GUI workflows)... |
|
I guess my view is: it's a card game, should try and surface the cards rather than plain text as much as possible in UI widgets so long as it doesn't seriously compromise usability. I think some of those usability issues above can probably be surmounted:
Agree with your Kozilek discard suggestion though, I'll look into that further... |

Example using Inquisition of Kozilek
Before:


After:
CardImageGridas a general utility for the deck-editor art picker; this PR takes advantage of it for desktop reveal and single-pick dialogs, so reveal/discard/exile prompts show thumbnails instead of a names-only list.CardImageGridis now generic over the item type via aCellAdapter;forPaperCardskeeps the deck-editor art picker,forCardViewsis the new in-match path.CardViewListChooserdialogs (counter types, colors, modes, spell abilities) stay on the text list — there's no card art to render.CardViewselection isn't part ofListChoosertraffic at all — it routes throughDualListBox(two-column ordering) orInputSelectCardsFromList(clicking cards on the battlefield), which are separate widgets with their own UX. Bringing the grid look to those is a larger change and out of scope here.🤖 Generated with Claude Code