You are correct that constraining X,Y won't give you linear velocity. To get linear velocity, you would need to do a different kind of mouse drag (in which you actually constrain linear velocity inst

(when touch is pressed - constrain self.position.x to game.touches.touch1.x and

levels. Then assign the level unlocked to a self attribute in the next available slot. So slot 7 is bought and it goes into the next slot and then slot 5 is bought so have rules that can track what i

When pressed it plays sound and randomly spawns one of 7 actors. You can see the random 'change attribute' 1-7, and #1 of the rules (again the others are identical apart from the variables, = 2, actor

I created an attribute called "random size" and set it to randomise between 1-3. I then attached 3 rules, you can only see one as I could not fit any more in the cap, but the others

@Jeffnichols the technique is actually fairly straight forward. You constrain your background actors offset to your camera controlling actor on both the x and y access. General principle is, objects t

Change Attribute self.TouchY to self.Position.Y

.....Change Attribute self.position.X to floor(self.position.X/game.GridSize)*game.GridSize+game.GridSize/2

for question 1 i believe what you want to do is - create a rule in the letters if over lap "your empty space for letter" then change attribute for position of the letter x and one fo

Constrain scene.camera.origin.y to game.devices.touch1y

It's hard to troubleshoot an issue without knowing if you are using Change Size, Change Attribute, Interpolate, etc., and then are you interpolating the width only, or the width and height, and if so,

Also, in many cases, it's possible to get away with using a Change Attribute instead of a Constrain Attribute when retrieving table data.

Well, there are a lot of instances where tables are useful without an additional attribute. I use tables all the time, and have generally reduced my global attribute use by 50% or better.

see.. when I learned that.. it really made me wonder then Why a table if it's going to be constrained out to a game or scene attribute..

At this point, direct entry isn't possible. The best way is to create an attribute to hold that table value, then make the rule reference that new attribute. Such as contain game.highscore to TableVal

Attribute condition block does not take me in that direction..

I've created a way to randomise size whilst constraining proportions by creating a randomising atribute then setting size rules for 3 alternates.

I've also added a timer which gives a variable random size when the bubble spawns. Unfortunately it doesn't constrain proportions and gives me elliptical bubbles as well as round ones.

Constrain the 'dot's' X position to: 512+(game.Accelerometer.Y *512)

But essentially you just constrain the dot's X position to a multiple of one of the accelerometer values.