PSR Continued

Ahhhh the "draw" court me off guard.
Fixed.
I demoed it to my better half while on the couch watching people spend wods of cash on pretty colors.
First peace of creative criticism is that the game is played on the 4 count.
When PSR is played in reality on a 3 count.
Reality 1. . . 2 . . . PSR.
Demo 1 . . . 2 . . . 3 . . . PSR.
The positives with the demo is that the user naturally picks there weapon on 3.
This avoids cheating the system.
BUT. . . it just doesn't feel right. I'll stick to reality for now.

PSR

Started on PSR (Paper, Scissors, Rock) about 2 weeks ago. No real visuals just the Ai.
Ai is just a fancy word that makes me feel like I'm giving birth to something that thinks. When really all its doing to generating a random number.
One in three.
So When the user is ready they press a btn and the script generates a random number.
That random number represents paper, scissors or rock. . . oh crap, I forgot about a draw.
What happens if there's is a draw?
I'll continue this entry later.
End of transmission.

Optimize Prime

I jammed what I have done together this evening. Just to taste the fruits of my labor.
I should be happy, but there is a hole stadium of room for improvement.
Optimization will be googled tomorrow.
I think it's got something to with the FPS (frames per second) I have it set at 30fps which is nice and smooth for a high-end PC but no so much for a little iDevice.

A, 2, 3 are on the table ;)

[Posted with iBlogger from my iPhone]

Wheel of DOOOOOOM!

I spent my spare time coding the "Wheel of DOOM" yesterday.
I was lucky this time. Things just fell into place.
I had one problem that i still don't really understand.
Think of it like The Wheel of fortune.
I have a "hitTest" running so a point or pin or indicator sits on a peace of the pie the WoD (Wheel of Doom) stops spinning on.
So if the "point" for augments sake lands on the "purple" peace of the pie the programs knows that It's PURPLE. Yes it can read colour.
The problem is that if the "point" is sitting literally on the WoD it bugs out.
I had to find the sweet spot for the "point" which was off the WoD, not even touching it.
I don't get it. I mean its a hitTest! . . the "point" HAS to hit (touch) the WoD to read the colour.
Anyway all that matters is that it works.

Oh yeah, pictionary works!!
But that's for another post.
No Picture today :(

K.I.S.S.

I went to bed already having a nightmare last-night.
Just when I thought everything was coming together I hit a snag.

The snag:
When "A" (card) was dragged into "B" (cup) I made "A" invisible deliberately, so "A" would be removed from the table.
But. . .
just because "A" is invisible to the end user (player) doesn't mean it doesn't exist in the program.
When Program "A" was run and finished we would loop back to the table with "A" invisible :)
The user would select "C" (a new card) drag it to "B" again and it would bug out because "A" was still there!
Solution:
table.removeChild(table.ACcard);

As simple as that. . .

Lesson - Don't code when your already fucked.

Here's a nice pick

D-N-D

I found a new but old way of tackling problems in AS3.
I find it hard keeping track of code even with labels if i put all the code in one file.
So I've resorted to placing the code on frames.
The downside is that there's a lot of duplicating code.
But that's as easy as a simple copy and paste.

I've had an issue with drag N' drop.
I can get drag and drop to work well, but I cant get flash to recognize the difference between the user wanting to D-n-D and the user wanting to select (click).
What I wanted was to have a drag-able button that you can also click.
Flash see's the D-n-D as a "click". So when the user starts to drag the object Flash registers it as a click as well. . .
So after stuffing around for a few hours I've come up with a simple and easy AND probably more interactive way around this.
Drag the object (Card) into another object (Cup) to activate the "selection" (Start mini game).