Moving to 'how do I' since this doesn't appear to be a bug report.
It's described in more detail in the offline games in Construct 2 tutorial. You simply reload the page to "install" the update.
I guess 'on size' is missing from the Browser object, will try to add for next build.
Ah, I think the problem is only with fullscreen apps and not windowed, I'll see if I can fix for next build.
I just checked and holding shift to rotate in increments of 5 degrees works in r101.
Moved to help wanted.
I think this was inevitable - open, free submissions quickly degrade in to, well, typical internet content. A fee is the quickest and easiest way (for them) to filter out 99% of the people who aren't serious.
Develop games in your browser. Powerful, performant & highly capable.
thehen - yeah, it would be straightforward with a plugin if you bundle a .cur file with it. I do think it's better to make plugins to workaround issues like this than to build them in to the main editor.
Just use the 'request fullscreen' action in the Browser object - the same way you'd enter fullscreen from a web page.
CrudeMik - either request fullscreen on startup, or make the window size smaller just for Awesomium.
It's been on the todo list a while, hopefully will get to it soon.
In testing for r101 I successfully published an app to the Chrome Web Store and it worked fine. I have no idea why it's not working. Can you share your .capx files that aren't working so I can investigate? Also if you bring up the Chrome Developer Tools (I think they still work for CWS apps), are there any errors etc?
Your .capx does not open, it appears to be corrupt and missing some image files...
The 'snapshot canvas' action calls 'on canvas snapshot' a moment later, at which point the system expression (IIRC 'CanvasSnapshot') has the JSON data of the image which can then be loaded in to a sprite or whatever.
madao17, your new .capx still uses the Dialog Box plugin. Please make sure it is removed from the project bar.
You're right, it was possible to name effects and instance variables the same, which should not be allowed. Should be fixed in the next build.