3
Replies
3
3
Replies
LEGEND
,
NS5,
> I am trying to do a simple Memory Game in Flash 8.
99% of games are not simple, even if they're supposed to be.
> The examples I have found are much more complicated
> than what this game needs to be so I was trying to create
> my own from scratch.
I applaud that! You will learn and appreciate to much more if you build
your own. Just don't think it'll necessarily be easy.
> Problem 1:
> When the user selects the wrong card that isn?t a match
> I need it to flip back over and set the variables back to 0.
> I can?t figure out how to do this without writing a
> conditional statement for each possible order the user
> could select them in.
Can you explain these variables? The ones you have to set back to zero,
I mean. Off the top of my head, I wouldn't use variables so much as
properties of my movie clip "cards." Give each card an instance name, then
add a property ... something like this:
cardA.face = "apple";
cardB.face = "apple";
cardC.face = "pear";
cardD.face = "pear";
cardE.face = "orange";
cardF.face = "orange";
cardG.face = "peach";
cardH.face = "peach";
And then when it's time to compare them, simply check this property of
each movie clip ...
if (clipReference1.face == clipReference2.face) { ... }
... where clipReference1 and clipReference2 refer to whatever movie clips
were selected. Does that make sense?
Show us how you're currently comparing two cards.
David
stiller (at) quip (dot) net
Dev essays: http://www.quip.net/blog/
"Luck is the residue of good design."
> I am trying to do a simple Memory Game in Flash 8.
99% of games are not simple, even if they're supposed to be.
> The examples I have found are much more complicated
> than what this game needs to be so I was trying to create
> my own from scratch.
I applaud that! You will learn and appreciate to much more if you build
your own. Just don't think it'll necessarily be easy.
> Problem 1:
> When the user selects the wrong card that isn?t a match
> I need it to flip back over and set the variables back to 0.
> I can?t figure out how to do this without writing a
> conditional statement for each possible order the user
> could select them in.
Can you explain these variables? The ones you have to set back to zero,
I mean. Off the top of my head, I wouldn't use variables so much as
properties of my movie clip "cards." Give each card an instance name, then
add a property ... something like this:
cardA.face = "apple";
cardB.face = "apple";
cardC.face = "pear";
cardD.face = "pear";
cardE.face = "orange";
cardF.face = "orange";
cardG.face = "peach";
cardH.face = "peach";
And then when it's time to compare them, simply check this property of
each movie clip ...
if (clipReference1.face == clipReference2.face) { ... }
... where clipReference1 and clipReference2 refer to whatever movie clips
were selected. Does that make sense?
Show us how you're currently comparing two cards.
David
stiller (at) quip (dot) net
Dev essays: http://www.quip.net/blog/
"Luck is the residue of good design."
NS5,
> Thank you for getting back to me.
Sure.
> I dont know how to explain my functionality better than
> what I did so I have uploaded the FLA file to my
> personal site so you can download it. It is the link below
As a rule, I prefer not to download files -- mainly because it forces
the developer to really think through what he/she has done, in order to
formulate a good question -- but I took a look in this case. Honestly,
I'm a bit confused by your approach.
Here are a few quick observations.
You don't need those _global variables. It's fine to have them, but
they just aren't necessary, here. If you want variables that are available
to any ActionScript in the main timeline (where all your code is), then a
normal declaration will work just fine.
e.g.
var myString:String = "some string:
var myNumber:Number = 5;
You can use the following in your MovieClip.onRelease handlers ...
card1a.onRelease = function() {
this.play();
};
... which is functionally identical to what you have, but easier to read, I
think.
Rather than keep so many variables (four of them), all you really need
is a single variable that keeps track of what other card, if any, was the
last one flipped. At the beginning, of course, no cards will have been
flipped, so you might do this ...
var lastCardFlipped:MovieClip = null;
Then the MovieClip.onRelease handler for each card should do the
following: a) cause the card to play through its animation; b) check if
another card has been flipped; c) if so, check if the current card's custom
property (discussed last time) matches the custom property of the last card
flipped; d) if not (meaning, if no other card has been flipped), note itself
as the "last card flipped" for next time.
First, you'll have to give each card an identity via a custom property.
cardA.id = "card 1";
cardB.id = "card 1";
cardC.id = "card 2";
cardD.id = "card 2";
cardE.id = "card 3";
cardF.id = "card 3";
// etc.
Then your event handler might be ...
carA.onRelease = function() {
this.play();
if (lastCardFlipped == null) {
lastCardFlipped = this;
} else {
if (this.id == lastCardFlipped.id) {
// this is a match
} else {
// this is not a match, so set lastCardFlipped
// back to null and start again
lastCardFlipped = null;
}
}
}
NOTE: These are off-the-cuff suggestions of mine; I'm not trying to
dictate how your game should work.
Obviously, you may want to add
features, move/change features, etc. I'm just hoping this at least gives
you something different to chew on.
David
stiller (at) quip (dot) net
Dev essays: http://www.quip.net/blog/
"Luck is the residue of good design."
> Thank you for getting back to me.
Sure.
> I dont know how to explain my functionality better than
> what I did so I have uploaded the FLA file to my
> personal site so you can download it. It is the link below
As a rule, I prefer not to download files -- mainly because it forces
the developer to really think through what he/she has done, in order to
formulate a good question -- but I took a look in this case.
Honestly,
I'm a bit confused by your approach.
Here are a few quick observations.
You don't need those _global variables. It's fine to have them, but
they just aren't necessary, here. If you want variables that are available
to any ActionScript in the main timeline (where all your code is), then a
normal declaration will work just fine.
e.g.
var myString:String = "some string:
var myNumber:Number = 5;
You can use the following in your MovieClip.onRelease handlers ...
card1a.onRelease = function() {
this.play();
};
... which is functionally identical to what you have, but easier to read, I
think.
Rather than keep so many variables (four of them), all you really need
is a single variable that keeps track of what other card, if any, was the
last one flipped. At the beginning, of course, no cards will have been
flipped, so you might do this ...
var lastCardFlipped:MovieClip = null;
Then the MovieClip.onRelease handler for each card should do the
following: a) cause the card to play through its animation; b) check if
another card has been flipped; c) if so, check if the current card's custom
property (discussed last time) matches the custom property of the last card
flipped; d) if not (meaning, if no other card has been flipped), note itself
as the "last card flipped" for next time.
First, you'll have to give each card an identity via a custom property.
cardA.id = "card 1";
cardB.id = "card 1";
cardC.id = "card 2";
cardD.id = "card 2";
cardE.id = "card 3";
cardF.id = "card 3";
// etc.
Then your event handler might be ...
carA.onRelease = function() {
this.play();
if (lastCardFlipped == null) {
lastCardFlipped = this;
} else {
if (this.id == lastCardFlipped.id) {
// this is a match
} else {
// this is not a match, so set lastCardFlipped
// back to null and start again
lastCardFlipped = null;
}
}
}
NOTE: These are off-the-cuff suggestions of mine; I'm not trying to
dictate how your game should work.
Obviously, you may want to add
features, move/change features, etc. I'm just hoping this at least gives
you something different to chew on.
David
stiller (at) quip (dot) net
Dev essays: http://www.quip.net/blog/
"Luck is the residue of good design."
AdChoices