Bug report time

t is the happiest of times :)

i just want to check wether this is just me (else i'll file reports), since it is a bit strange:

• start a fresh construct 99.2
• open a new dx runtime, go straight to the event sheet
• double-click the event sheet, but click 'cancel' in the dialogue
• repeat the above 2 more times
• on the next double-click, the dialogue does not show up
• on another double-click (or any other interaction) construct closes.

another one:

• fresh construct, fresh layout, straight to events
• add an event, use any system object condition, finish adding the event
• add another event, select the system object, click next ...

kills my construct everytime. how about you?

thanks!

sorry for being off-topic, but: nice avatar, xiao ;D

well, the beauty (& potential) of a feature is in the eye of its users :)

you never know what people might come up with, so i'm a strong advocate of offering as many entry points as possible.

ashley, it would be very nice if you could spare the time to drop me a note (or wikipage) describing the format; i'd really like to try this, but i'm too much of a scriptkiddie to seriously unravel constructs source code.

i really appreciate the new feature, and i was wondering if it was possible to edit the meshes in any other editor, since i've never heard of the .mesh format before.

if that's not possible, i'd be interested in the rationale behind inventing another 'proprietary' format versus rolling with any of the existing, widespread & readable ones...

? :D

Construct Cupboard Cutting Crew

re-build a cupboard from scratch!

instructions ingame

all images stolen from the internet

download .cap (made in 98.9)

download .exe

sounds very cool & like a reasonable plan! i'm confident that you will continue to rock! thanks for everything.

i guess this is not a bug with while, but a bug in how objects persist in the timeframe of a single tick. i think that the 'pick random' condition picks a random object from the set of objects present at the start of the current tick, and ignores any changes (objects being destroyed) made to this set during the current tick.

i've had similar problem with objects that are not present in the first tick ('destroyed on startup') and created en masse in a loop during the 'on startup' event. because construct couldn't operate on these objects in the same tick, i worked around that by 'call function after delay'. i though it was a startup thing, but your 'while'-problem is oddly similar.

does this ring any bell with the devs regarding object handling?

http://en.wikipedia.org/wiki/High_Level_Shader_Language

my 15" macbook can be carried in a small messenger bag, but it's quite a strain on the back, so i mostly opt for a backpack anyway. a friend's 17" still fits in a slightly larger bag, so it's just as portable, if slightly heavier.

however, i could not do serious work on my 15" screen; not only is the fact that it's attached to the keyboard ergonomically challenging for me (because my hands and my head are quite a distance apart when in any comfortable position), but it's also too friggin' small. i've got friends that can work on small screens with ludicrous resolutions, but i'd prefer a physically larger screen to a higher resolution every day. so my tip would be on the 17"; for slightly better posture and prolonged health to our beloved devs! :)