Mmmm - at first it made no sense when I changed the primary event sheet for No 2, but I think there was a browser cache problem. It appears to be working correctly for me now...

X is "horizontal" (rows), y is "vertical" (columns).

Because of the way the loop works, x then y makes columns. So the first loop, x=0, runs the y loop - 0,0 | 0,1 | 0,2 | 0,3| ... | 0,7 - after completing, the next x loop runs 1,0 | 1,1 | ... and so on.

Basically when you have y as a subevent of x, each entire y loop has to finish per loopindex of x. When you take the x loopindex as the y coordinate and vice versa, the position in which they get placed gets inverted as well.

newt nope, that what i was thinking also but is as oosyrag says well kinda...

its like this if i remember properly.... no matter which way it is... for u to get

1234

5678

you need to make a loopindex(x)*10 / by something forgot the formula and then u get it one after each other. il be back with it.

edited: i know is been 2 years sorry for bringing it up, but the math i was talking about was

loopindex("x") +loopindex("y") * number of loops for each for example

if you have a

for "x"

from 0 to 4 (which is 5 including 0)

for "y"

from 0 to 4

we then get the value bellow

5 = x.N_horizontal_loops = number of loops on the horizontal lines counting 0 as 1 (so 0 to 4 =5 0 to 11 = 12, this works even if you have loopindex y loops greater than nr of loops of x)

yeah it depends on how you look at it but for me X is always the row and Y is the columns... I hate the way C2 says X is the width.. and Y is the height.. it's completely wrong to me. Height should be the number of rows or "records" and width should be the columns or fields