(Quote)

I went into my image actor and told it to constrain 'self.image' to tableCellValue(table,N,N)

But I would make a separate actor call it knob or something, constrain its position to match your wand actor (your A and B actor) but with an offset it so that its position would always be Position A

Change Attribute: self.yOffset To: self.Position.Y - game.Mouse.Position.Y

Exactly ! And that is how GameSalad looks at the number 16 too, whether it's come from an equation, an integer attribute or a real attribute or a user's touch input or the device's clock (etc etc), it

(Quote)

If you interpolate an integer attribute and display text ( query the value of ) that attribute during interpolation it will display a real value so during interpolation GS is storing a real in an inte

. . . . I've just read this number from an attribute, can you tell me (simply by looking at the number) whether that attribute was an integer or a real attribute ?

Yes, you cannot store a real value in an integer attribute.

(Quote)

Agreed, when an actor is at x=20.3 and you display the actors x co-ordinate - and the actor's x co-odinate is a 'real' attribute, using a Display Text behaviour it will display 20.3 . . . . and the ex

But when I use Change Attribute and set TileWidth to 9.7, it rounds it to the nearest integer 10.

What !? There is not 'front end' and 'back end' that I'm aware of, the reason you can interpolate the tile width value through decimal places is because the tile width attribute is simply storing a nu

The tile width attribute is an integer, like I say 'integer' or 'real' only applies to the storing of values in a attribute. The interpolate behaviour doesn't set anything to real (or integer), it sim

If it is ever a real, then it should let me manually set it or use change attribute to a real.

-Attribute game.mouse position y < (y coordinate of the menus bottom part here)

But when I added a change Attribute behavior to 9.7, I get a 10.

Basically; I have a constrain behaviour which constrains an actors rotation to the touched location of the screen. So basically if someone touches the top left of the screen the actor will rotate to f

The display will read 20.3 if the actor is at x=20.3 - rather than 20 -regardless of whether the coordinate attributes are real or integer.

Once a value has been read from a real or integer attribute it is no longer real or integer, it is simply a number - so in that respect there are not always integers (if I understand what you are sayi