Month: February 2013

Please note, this blog entry is from a previous course. You might want to check out the current one.

Your Set game should also report (mis)matches like Required Task #3 in Assignment 1, but you’ll have to enhance this feature (to use NSAttributedString) to make it work for displaying Set card matches.

In storyboard copy the label from the card-game view to the set-game view and connect it to the set-game view controller. Change it from “plain” to “attributed”.

In updateUI create a new attributed string which derives from the last-flip description. Update this string with the card attributes in the for loop and – at the end – use it for the label text:
Continue reading “cs193p – Assignment #2 Task #8”

Please note, this blog entry is from a previous course. You might want to check out the current one.

Your Set game should have a Deal button, Score label and Flips label just like your playing card matching game from Assignment 1 does.

In story board copy the flip and the score label as well as the deal button from the game card view to the set card view and link them to the appropriate outlets in the set-card view controller.

The complete code is available on github.

Please note, this blog entry is from a previous course. You might want to check out the current one.

Instead of drawing the cards in the classic form (we’ll do that next week), we’ll use these three characters ▲ ● ■ and use attributes in NSAttributedString to draw them appropriately (i.e. colors and shading).

In story board change the title of the buttons from plain to attributed. Inside the update function generate an attributed strong from the card contents. Check if the current card is a set card and update the attributes using updateAttributedString:withAttributesOfCard:, which we will create next. Finally set the adjusted title off the button:
Continue reading “cs193p – Assignment #2 Task #6”

Please note, this blog entry is from a previous course. You might want to check out the current one.

Your Set game should have 24 cards.

Add 24 custom buttons in storyboard and link them to the cardButtons outlet and flipCard: action method in GameViewController (the parent of SetGameViewController):

Continue reading “cs193p – Assignment #2 Task #5”

Please note, this blog entry is from a previous course. You might want to check out the current one.

Choose reasonable amounts to award the user for successfully finding a set (or incorrectly picking cards which are not a set).

Create three new properties for CardMatchingGame to replace the previously used constants:

@property (nonatomic) int matchBonus;
@property (nonatomic) int mismatchPenalty;
@property (nonatomic) int flipCost;

Continue reading “cs193p – Assignment #2 Task #4”

Please note, this blog entry is from a previous course. You might want to check out the current one.

The Set game only needs to allow users to pick sets and get points for doing so (e.g. it does not redeal new cards when sets are found). In other words, it works just like your other card game (except that it is a 3 card (instead of 2 card) match with different kinds of cards).

In this task we create the actual cards and its deck … and hope that everything is ok because we will not able to test it till later (we could add some unit test, but …)

Similar to PlayingCard, add properties to hold the color, symbol, shading and number of symbols, and provide class methods to access its valid values:
Continue reading “cs193p – Assignment #2 Task #3”

Please note, this blog entry is from a previous course. You might want to check out the current one.

Don’t violate any of the Required Tasks from Assignment 1 in the playing card game tab (in other words, don’t break any non-extra-credit features from last week). The only exception is that your playing card game is required to be a 2-card-match-only game this week, so you can remove the switch or segmented control you added for Required Task #5 in Assignment 1. Your Set game is a 3-card matching game.

Start by moving “everything” which is not matching-card specific to common game view controller. Note that all property declarations need to be in the .h file as well as those methods you need to access from your subclasses and from storyboard (e.g. action methods).
Continue reading “cs193p – Assignment #2 Task #2”