https://github.com/nwjs/nw.js/wiki/Extr ... -about-gpu

Did not understand but seems to be exactly what you actually want

Last time I checked it was not possible with vanilla C2, a launcher might be a possibility to achieve that, even though that feels cheap

megatronx I was not describing an issue but the concept of why it works fine, unless you have different scales rate in which case you have to take that into account and so scale every layer independently.

At least erasing it massively seems easy enough, to prevent it without being too "hard on newcomers" however would not be easy to do.

Ashley well that was fast, thanks a lot! Spam is a pain when you want to see new posts.

sqiddster if it can help explaining it, set canvas size basically change the window size propriety of the project at runtime, just that sentence explains that the low quality fullscreen changes with it, then the layoutscale just helps compensate that as long as you do not have differents scale rates for the layers.

I know it is clearly visible but today it seems there are a lot of spam, notably from this account https://www.scirra.com/users/gongsakwan

Most are named "＼＼『ＭＸＤ７。ＣＯＭ』＼＼[some non latin characters that can vary]"

PhoenixNightly I agree on the fact no programming knowledge is needed to an extend, however most issues with users seems to come from three facts:

-Sometimes they did not designed the part they want to implement enough and so, do not know how to implement it (if someones want to build a car or a bike without any plans, well good luck, if they did plan ahead it becomes much more easy as you just have to do it, same goes for C2, if you do not know enough what you want to do, you cannot simply translate it to the event system, some call that designing part programming or coding but I disagree, it is more designing at that level as you do not have to take any limitations in account at first, only when implementing it).

-Sometimes they did describe it fully, but just have no idea how to implement it, in which case asking the forum often solves that issue.

-sometimes they either implemented it wrong or relied on a specificity of the system they should not rely on but think it is "fine enough".

shinkan by " their fault" it is obviously about those who bought it after this decision, and even then it is their fault the same way if someone recieve spam in his e-mail adress it is his fault for putting it somewhere, they are responsible but lets face it, when that much people do that mistake, something is just wrong elsewhere and blaming the user only goes that far but will not correct the issue, which was the point of the end of the parenthesis (in the case of spam: spams should not exist and just putting your email should not be that dramatic of a decision but in the end it can be a big issue, in the case of C2, people expect it to have native, why I do not know and that is not my job but scirra's one to figure that out)

newt also the only one that is barely used for something considered "serious" for some reason, I did hope that when the arcade would be there, the html5 export would get the love it desirve for, you know, being the only exporter that actually is maintained entirely by scirra as is (a user can understand some browsers issues and expect them, for an exe though or an apk, that is pretty hard to swallow, "you chose the wrapper you should have known!"), I do not mind the absence of native exporter at all (even though some people seems to have missed that part when buying it, entirely their fault of course but it could maybe have been clearer), but the html5 exporter could have some features that are currently only for wrappers for no good reasons, or a better connectivity with social network, whoch would also be there for the html5 of C3, just my two cents.

As for the paid update, does not seem that bad in all honesty, if it becomes what they said it will be (more opened to third party plugins, the editor working on more OSes, better stability and most of all maintainability of official plugins) I would say it is fair, but for now, C2 should be fixed a little more so we can call it a finished product (once again my two cents, I now my opinion is not much as scirra obviously can do everything they want, the market shares will decide).

Apart from wait, create object, and async. Actions , everything is done in order from top to bottom, an action is over before the next one.

every tick add 1 to variable

Variable greater than 6, set it to 0 . [...]

If variable equal 0, [...] find path

Be sure that the event to set it to 0 does not occur right before checking it, or more simply, use a time difference, it is more adapted to your use.

create object and spawn another object are not done before the next top level event (aka the next event that is not a sub event of another one).

For every async conditions, there is a trigger associated with it (local storage, ajax, etc..)

If you check a value and do a loop, just see the order you did it, the loop comes first? Then it will check the value everytime, it is after? Then the oppositz, the value is checked before doing the loop.

Sequencing can be problematic since the time between two events can vary (heck even if it was not the case, switching to a display of 120Hz would make it twice as short as a 60Hz display).

Never used while loops as I prefer to use for loops, but maybe they are more flexible, be sure that it will not be endless.

nimos100 thanks.

Nesteris I was asking because just looking is not enough as in a lot of cases it seems to be a misunderstood of the feature, not it not working correctly, the platform behavior slope by itself is not a bug, just something not wanted , the not being able to fall however is one (if it could be redone however I would not mind, I remember it breaks the point of having a platform you can fall from with the jumpthru behavior, as you can climb back on it too, being able to keep slopes while correcting that would be far better), the on key pressed is a trigger and so is meant to happen before anything else (it happens at the exact time you pressed it, where key is down waits the next check), however being able to choose when to refresh behaviors would prevent that issue I agree (That would also fix the pin issue).