In Mtgdb.Gui each card face is represented as a separate card. You have in your collection a card named `Alter Fate` which you will see if you turn on displaying textual fields.
If you want to control which side to see:
- add both faces to collection
- add to search bar
to see only creature side
- Code: Select all
layout: NOT adventure OR Type: Creature
to see only adventure side
- Code: Select all
layout: NOT adventure OR NOT Type: Creature
Additionally, it lets you search by type, text and properties of other side when search is restricted to cards from collection only (or from deck only).
I can see the flaws:
- you get +1 card counted in your collection
- you have to do manually add both faces to collection (or deck)
It may not seem a difficult thing for application to handle automatically, but it is, if you consider:
- there are different multi-face layouts, some with > 2 sides, such as meld.
- some cards have namesakes within a set. Suppose you added (or removed) card's main face to collection, then which alternative face (which card number) should be atuomatically added (or removed) if there are > 1 matching candidate? What happens if card data from mtgjson.com is slightly corrupt, so the mapping of faces is A1 -> B1, B1 -> A1, B2 -> A1
- alternative faces should not increase collection / deck count
- alternative faces should not increase count / total price in deck / collection statistics diagrams
It can all be handled, but it's a big and error prone task so I'd rather not do it.