The blue sprite is meant to turn invisible every 150ms, and turn visible every 300ms. It does work... but very poorly. For some reason it's flickery and inconsistent

Did some tests with the .cap. If you let it run with unbounded fps, blue sprite becomes very consistent. My guess is with vsync on, the time in which something is displayed and the time when it's calculated is slightly different, so tiny measurements like this will be inconsistent. Construct is double buffered I think, triple buffering mitigates these things somewhat but not completely. This is why I prefer doing things frame-based when the timing's really tight (and it doesn't affect logic).

I can't make heads or tails out of "else". Tried making it a subevent and it does flash... for like a single frame.

Up there, between "User Control Panel" and "PM" links.

Ugh. Facepalm.

Where is this chat thou speaketh of? Ofth?

I know I saw the details somewhere but not forums nor wiki search reveals them.

ummmm feature request:

mantain aspect ratio when stretching options: touch from inside, touch from outside (as seen in Media Player Classic). I shall make a thread for it in feature requests

flashing based on frames is still useful though... in old-school games transparency was made this way and it stuck around even when not needed anymore.

On respawn set invulnerable and flash every other frame, etc, and you could coordinate complex flashing patterns between different objects for visual trickery.

I'd use both.

lol HD graphics

wow XNA export

>

> > EDIT: Also, you can play in fullscreen if you press F2 if you think the screen is to small.

> >

>

> No I can't, my monitor doesn't support 320x240

>

Oh. Know what I can do to fix that?

in Application properties, under Window Properties, enable the Maximize box and set Resizing to Stretch Window Content.

Must be a shader thing, doesn't work in mine either (Radeon 9600xt)

:O indeed it does!

I never saw that page with the shortcuts before, will keep it in mind

Sometimes two objects (or more) overlap in a layer and you want the one below.

I've seen design software that lets you keep pressing mouse1 (without dragging) and it start cycling, picking objects below until you let go mouse1.

Another one had a modifier key and if you click an object it will select the top one, click again without moving the mouse and it will select the one below instead, etc etc.

It'd be nice

Can't that somehow be streamed? I mean, always load the current layout and always already start streaming the previous and the next layout into the vram - and kick out everything else.

If you jump to a layout that's not the next, you'd get choppyness.

That said, it would be cool to hint a preload.

Like an action: load layout x into VRAM

you could trigger it with enough time and if there's not enough time, well, choppyness.

And which was the problem?