android is so much easier. why does apple have to make things so damn complicated?

Exact same way as the row. make a Game.col and a Self.col and set the value based on where the change scene trigger is going to.

so how does one define a column value in an attribute? presumably in the exit trigger actors i create a new integer 'column' just like row and i change the 3, 7, 11, to self.column?

the row/index is defined correctly. It just doesn't understand what column to use because it has 3 possible columns available, and it looks like they all can trigger unrestricted.

done the display text showing the game.row value and thats correct.

Oh, and if you have 3 change attribute groups for x/y with no rules defining when to trigger, they would all trigger on a scene change. So depending on what's last to trigger, that would be where it e

Is self.row being defined by a rule, single change attribute, or a value preset on the actor? Have you tried using display text on an actor that's on every scene to show the value of game.row after ch

You might start with this and see where it takes you: http://forums.gamesalad.com/discussion/30842/free-calculator-template.

New free tracks are waiting for you:

You're very welcome! (Image)

I just want to thank everyone who has joined the Lyfesaver community! We are slowly getting more questions every day. That being said, I would love to have more users be apart of the community to try

I am currently available for freelance work. If you have a project you would like me to work on with you, please feel free to to contact me at cgrobelski@gmail.com

But yes the app will not be closed - it will be in an art gallery and there will only be limited keyboard access in case a member of the public wants to be dodgy. So the idea is that it will stay open

* Starter Templates (for you to build on)

First I need a text box that I click on that will alow me to input decimal numbers. Second I will need to make it either add or subtract the values of another text box that I will need to do the same.

@Riffel good job, you did an excellent job on capturing the feel of it. I especially like the very realistic weightiness and dynamics of the ball!

@NNterprises , thank you I'll try that

I sort of do, I think ? But I'm not sure what the issue is ? Is the question 'how do you get two actors to exchange information' (if I understand the question correctly ?)

oh snaps @Socks i noticed that you edited the code in the actual prototype and not the actor... but for this it would need to be spawned so i would need it to be in the actual prototype... you know wh

you learn to love it