So is the first bit a boolean attribute?

I then ended up with a prototype avoid the squares game, and in the mean time had learned about objects/actors, controls (accelerometer) and behaviours for collisions etc.

Just uploaded a watered down version of the action. If they could spin based on physics that would be great but I couldn't make it work (tried constrain) I don't them to float around. I guess I coul

Change attribute score = 0

when player loses life change attribute game.score to 0

For the life of me I can't straighten this out. My actor will not rotate until an attribute is true(touching a button I have this working) and it overlaps or collides with another actor but I want it

Change Attribute self.DragandDrop to true

In the first scene add Change attribute behaviors to the original actors: when touch is pressed, change attribute game.button1 to 1, the same for the second actor, but with attribute game.button2.

Actor A catches actor B; motion attribute for actor B is set to 0 for both x and y

another way is to just have a simple change attribute in your button as pointed out by CodeMonkey quite recently.

Create a rule so that it says if the plate touches or overlaps with the dropping item. Then put a constrain attribute behavior in the rule that constrains the plate's X and Y motion to 0.

Also you can make a integer attribute, and create a rule in the first actor:

another way is to just have a simple change attribute in your button as pointed out by CodeMonkey quite recently.

Hi Dave, that's no prob. you need a scene or a game boolean attribute. You leave it unchecked as false.

Can i have an Integer Attribute and a Real Attribute and then add them together and still get the correct answer, in decimal???

sequence so that I was able to use a change attribute behavior with the ".." thingy. I also used a similar setup for the star waypoints as Orbz's waypoint demo so that I could just

Create a rule so that it says if the plate touches or overlaps with the dropping item. Then put a constrain attribute behavior in the rule that constrains the plate's X and Y motion to 0.

Not on my GS machine at the moment but I have had that transparent trick a few times...pushing the envelope with attribute combinations...the first time was quite a shock!

Make game real attribute called Timer (OK, call it Time to avoid confusion with the behaviour called Timer)

The color option has alpha set it to 0 then when certain game attribute or collision happens change self alpha to 1