Okay, i calmed down and was in a better mood today lol, so i decided to spend this sunday playing with construct.

I'm so impressed, i don't know what i must of being doing before but now it totally blew me away. Maybe the problem was inpart that using mmf for so long i've gotten used to always using work-arounds which has got me into bad habbits. Construct seems to take a more logical and ordered approach to everything and is more like real programming.

I think i'll have a hard time going back now.

Good work on the rain demo. Theres really no better response to this argument.

No, the code above was just a test, nothing i code seems to work so i wanted something easy which i knew should work, but it doesnt seem to.

No behaviours, no other code.

I'm a bit fed up with the program at the momemt so i'll cool off and try again later.

I'm sure it's down to me just needing to get to know how to use the program better, but i just can't seem to get even the simplest of programs to work using construct.

For example i do,

always

• set box.x to mousex

• set box.y to mousey

and even that doesnt work, it just stays in the top corner.

Forget about doing anything remotly complicated.

[bug] When i try to change the background to a custom colour in the layout properties panel it says "an unsupported operation was attempted".

You can download the cap. file here,

http://www.mediafire.com/?k1plldp7hnm

I really like that idea.

Incase you missed the other thread, the platform behaviour gravity directions are not working, and i can't get max fall values to work, don't know about the other properties.

I've applied platform behaviour to a box and set the gravity direction to up instead of the default down but it still falls down. Same if i change it to left or right. I've tried setting all other values to 0 (exceot gravity strength) to see if that has any efect but it doesnt.

Am i doing something wrong or is it a bug?

okay i had them in the same condition box, when i put the "for each" condition into a "sub-event" instead it works fine.

Can i ask what the difference is?

i can confirm it's the "for each" condition causing the error, when i remove it the app runs fine.

I see now. The 'for each' sounds very nice.

I've tried it but when i try to run the app i get this error

"Temp.exe has encountered a problem and needs to close. We are sorry for the inconvenience."

I add a box to the frame,

I create the condition "always" then action fastloop "fall" no.of boxs amount of loops.

Then next event condition, on loop "fall", + condition "for each box", then the action set box.y to box.y +1

Then i get that error.