I have created a boolean attribute named snap and added it like you said but the actors still move.

I'm following along with one of the popular GameSalad tutorials on youtube, but its using the mac version and I am using the Windows version. In the video, he sets a new attribute "slider_bar

just create a game attribute to know when you click

when mouse button is down and touch is pressed constrain attribute self.positionX to game.MousePositionX and constrain attribute self.positionY to game.MousePositionY. It should work, if it doesn't, l

change attribute: game.unlock To: game.unlock+1

I thought save attribute places some file/data to the phone, so if I turn off/reset my phone the data will be available when I open the game again.

Only option is to Constrain the x and y values

Wayne made a tetris with GS a while back and he made the blocks constrain to a master so im guessing this is lots of small squares too?

How (if possible) can i constrain an actor to touch, but with the offset of where the touch is?

Is there like an attribute or something? How do you code it so the scene only takes as long as the actual loading does?

Such as developer6810 says you must make one attribute a level. You can use this rule but you must use a different attribute for each level.

The reason this happens is because you're using the same attribute (game.overallscore) for each level. So, when you save it, the computer can only pick one number and use that for each level. Try maki

When (attribute) self.time > (the number of seconds you want this actor to exist,

@kevinjcamps, try to create a game boolean atribute (start) to know when the scene starts. then in each actor create a rule saying when attribute start is true change attribute self.movable to true an

or equal to) game.levelonehighscore then change attribute to game.levelonehighscore to game.overallscore. So now game.levelonehighscore has 1200 . I do this too all my 3 scenes. so its game.levelones

To save performance you could use the change instead of the constrain. But if it not affect the game then go for it. (Image)

Hey Gyver, it works great...the only change is that i don't use a change attribute, i use a constrain attribute because i also want the time to display...

@robert.mccarthy ... I would do a Game attribute.SecondSliderActive is touched change to true. Then on 1st sider put when secondSliderActive is true constrain self.positionX to Global variable.

(Quote)

All works great, moving the slider changes my global attribute.