You'll get a better response if you explain in more detail, and maybe post the .capx file.

I don't know if it's been fixed -but i'm pretty sure having groups underneath a For each condition used to break it.

See if placing one as the first event in each group fixes it

This probably isn't the solution to the problem, but you should use *dt instead of /60.

dt stands for delta time and is the amount of time (in seconds) since the last tick... so it'll change with any frame rate dipping.

Micro-jitter of 1 pixel makes me think of the 'pixel-rounding' project property. Other than that I'd suggest posting your capx

sqiddster, It sounds like I have a similar problem, where, for lighting, I have a black layer with the blend mode 'multiply' which basically darkens everything that's not lit up, however I want the background layer to be unaffected by this darken effect and to retain it's own brightness (due to it being in the far distance)

You said 'source atop' works? What did you apply this to? I've tried a few things but nothing seems to be working.. thanks

7Soul, reread what you quoted.. E creates an event and opens the conditions window, if you close that then it deletes the space. I can't speak for everyone but frequently all I want is the blank event to copy and modify existing conditions into the space.

Global and instance variables grouping would be very useful.

this is what currently takes up an entire screen on my current project

https://dl.dropbox.com/u/53374990/Forum/GlobalVars.png

For storing objects though.. it seems what you described you can already do that with UID's

for example:

For each character

create HPbar

set instance variable character.HPBarUID to HPBar.UID

And then when you need to pick that HPBar you just need "pick by UID character.HPBarUID"

Rory

I think for saving dev time, the ability to select and edit properties of multiple layouts is the most important thing on the list. Handling a 20+ layout project and wanting to change one thing is such a pain in the ass.

by the way I feel like this reads as one massive moan, but really I love c2's interface.. it's much better than stencyl and gamemaker.

You could either leave the origin in the centre and have it snap to a 16x16 grid

or set it's position alongside rotating it like:

set angle to 90

set x to self.x+self.width

but of course a different position would be needed for each angle.

If you need them to rotate more than once, so it works regardless of their current angle, you could have an imagepoint in each corner.

So for rotating 90 degrees:

set position to self.imagepoint(TopRight)

set angle to self.angle+90

and for rotating 180 degrees

set position to self.imagepoint(BottomRight)

set angle to self.angle+180

etc

ps: this should have been posted in the 'how do i' forum

Yep that's right

but why not just try it yourself?

I think you could do this without different layouts.

Have you tried the fullscreen modes? They allow for the viewport to scale to meet the browsers size

also there is a system action to set the canvas size

Rory

I know right? it's a bit crazy

SullyTheStrange

I completely forgot you could do queries within expressions so thanks for the reminder..!

However that way won't work for when the number has one decimal place. 456.1 would still display 456.1 instead of 456.10

Ashley yep it's working thanks

New bug though:

If you have a blend shader alongside a colour shader.

For example 'lighten', and 'set colour'

The shaders position seems to be clamped within the viewport

preview

capx