Our most stable build ever!

you guys are just experiencing a new found stability, it might take a bit of getting used to though

i haven't actually tried it out yet but my guess is that the keys on the numpad are meant to by hotkeys for the action point and hotspot

7 8 9

4 5 6

1 2 3

the resulting positions of the points after pressing the numbers should correspond with the placing of the numbers on the num pad

so pressing 1, 3, 7, and 9 will place the point in the corners, 2, 4, 6, and 8 will place the point on the sides and 5, in the center

i forget is 0 does anything

i think Ashley meant changing the hardcoded values in Construct's code

Happy Holidays to you all too!

wtf!?!?!?!?!?!?!?!? lmao! that must have been illegally transported from the future! quick! do as much as you can before the time patrol finds you!

what is your layout size?

are you trying to scroll the display or the object?

when you want to expand the layout upwards are you trying to do this in the construct or at runtime?

application properties

http://i163.photobucket.com/albums/t294/vinnyang/appProp.jpg

layout properties

http://i163.photobucket.com/albums/t294/vinnyang/layoutProp.jpg

actions for display settings

http://i163.photobucket.com/albums/t294/vinnyang/display.jpg

if this doesn't help, you can send the cap file to sensationsoftkgp@gmail.com

okay, i've gotten off my lazy ass and tried something else and it worked so either i don't know how to properly use sub events or i've managed to find a bug <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz" />

this is what i did

• deleted the sub events under the left and right key is down conditions

• made a new event:

+ Key Left arrow is down

+ Sprite2.Value 'agility' Less than 10

OR

+ Key Right arrow is down

+ Sprite2.Value 'agility' Less than 10

: Sprite2: Add 1 to 'agility'

that encompasses the same idea as before but for some reason it works this way and not the other

i was taking a look around in construct and i noticed that there's no way to retrieve the size of the layout in the expression editor, probably not a high priority task but should be included anyways

with regards to the scrolling, there are two things you must first understand: window size and layout size

in the application properties, you can set the window size

in the layout properties you can set the layout size

so setting a layout size larger than the window size will allow you to scroll the layout provided that you have created events to do so

setting a layout size smaller than the window size will however will display the layout in the top left corner of the window and only objects that are in the layout (even just a tiny bit) will appear in the window, anything else will not display

hmmm, the for loop seems to run itself automatically ... =S lol

could you explain it a little further? i'm not really sure how i would go about accomplishing this with a for loop <img src="{SMILIES_PATH}/icon_razz.gif" alt=":P" title="Razz" />

moving a sprite 3 pixels once and moving a sprite 1 pixel 2 times are 2 different things when it comes to collision detection which is why i do the movements in the loop.

without the loop it would check for collisions every 3 pixels whereas in the loop it would check for collisions at every pixel which is especially important when sprites start covering larger distances in a shorter amount of time

well the agility acts like speed in determining how many times the loop needs to run so it must always be 0 or greater (there should be an event resetting agility, i just haven't added it)

the subevents in the loop determine the direction

so the idea is that with a higher agility, top speed is reached quicker (speed is capped by preventing agility from increasing beyond a certain number) and the loops are there for pixel perfect collision detection (i just haven't added the conditions for collision yet -_-' lol)