Closing, please see the physics tutorial. Other behaviors/events moving Physics objects has the effect of teleporting them, so physics collisions will no longer work as expected.
Closing, please follow the bug report guidelines (attach a .capx, etc)
Closing as by design: the parameter is optional and the expression can be used without it, so it doesn't suggest to use a layer parameter. It is however documented in the manual.
Develop games in your browser. Powerful, performant & highly capable.
Closing, please follow the bug report guidelines and provide steps to reproduce or there is nothing we can do about this report.
Also consider pressing 'Reset dialogs' in Preferences and checking your graphics driver is up to date.
Also seems to work fine here, with node-webkit 0.11.5.
I think this is a node-webkit bug fixed in v0.11.5 which we just put up at scirra.com/node-webkit. Can you confirm it's fixed there?
Can't reproduce, works fine here. Please make sure you have the latest version of node-webkit installed from scirra.com/node-webkit.
You do not have permission to view this post
Thanks, should be fixed in the next build.
Closing, please file a new report if you can reproduce the problem in r192.
Closing, please follow the bug report guidelines.
Closing as won't fix: as of r192 we no longer officially support Ejecta. Consider using Cordova instead, or if you are desperate, file a bug with Ejecta instead.
Closing as won't fix: the mouse event goes to the text box instead of the game, and creating the text box half way through a click prevents the game seeing mouse up so it thinks the mouse is stuck. Like you say the workaround is straightforward.
Closing as not a bug.
Sorry, nothing we can do about this, it's just what the browser does.
Try working around it with continuous mode and just ignore any results that come in while not holding space.