Holy smokes @Socks that is an excellent answer I really appreciate that. I will always now make that apart of my "tidy up" procedures. Before I was just doing what @Lost_Oasis_Game

You have 12 layers, going from 1 at the bottom to 12 at the top.

I had remembered you soecifically saying actor code top to bottom. Had no idea about the layers in which the code id executed. Not that at the moment I can say how that helps me...but at least now I

Better way to say it is layers bottom to top. Actor code top to bottom. I remind people of this often in my videos.

(Quote)

Go to bugs.gamesalad.com, click NEW at the top, then CREATOR and then fill out the form to describe your issue, and upload your demo there as well. Make sure you tell them to run the demo more than o

Rules and behaviours will normally be run from top to bottom. GameSalad does NOT guarantee order of execution, though, so if you must have x happen before y, you need to force it using a rule or timer

im kind of confused with something , i saw videos that say that the rules trigger from top to bottom and i saw posts that say rules trigger from bottom to top, which one comes first ?

you need to rotate the screen till its at the top. I set it up with a rule for three attributes. When the actor, location, and x or y accelerometer (always set to 1 or -1) match up it goes repeats

(Quote)

I agree that when the device determines the oreintation...the ad will end up viewed top or bottom...I would not EXPECT it to display sideways.

And it was recently said by a GS programmer that attributes don't work top to bottom like some other programs, but rather use a notification system{although the lines of code running through actors mi

the first ball) - it will land neatly on the top of the first ball, even after bouncing for a while, whereas in the real world things are a bit noisier, factors like the quality of the surface (even

(Quote)

instructions right. But as the arrow in the hud layer sees itself on different coordinates as the object in the scene I thought that might be why it's not working?

It sounds like you're changing the value of one or more attributes and you have rules that destroy the tabs actors based on the value of those attributes. If you don't want the tabs to be destroyed,

Thanks Socks. The trouble I've had though is that the coordinates in the HUD layer are not related to the scene, but rather the position within the screen size / camera. For example, let's say my sc

The above will get the arrow on your non-scrollable HUD to point to the object on the scrollable layer.

(Quote)

I'm trying to get an icon in the hud point to an object on the scene, but it looks like the coordinates of the hud (defined as a non-scrollable layer) refer to the screen size not the scene size. To