Ashley's Forum Posts

  • — - they may work with single-touch in r90, providing you set 'Use mouse input' to 'Yes' in the Touch object. WP7 only fires mouse events for touch so there's no multitouch, but if the Touch object is receiving mouse input it can work.

  • Good idea, I'll do some performance tests at some point. I doubt they'll show up a CocoonJS vs. directCanvas performance difference, but they should still give a good rough idea of sprite counts you can get away with and mobile vs. desktop performance.

  • —: the 'Keyboard' object in your project became corrupt. I've recovered the project and it works now:

    http://dl.dropbox.com/u/15217362/officialgame-recovered.capx

    Obviously we want to prevent this ever happening again. Can you remember what you were doing just before the problem started? Did you do anything with the Keyboard object in particular?

  • gonzdevour - you really need a phone to check it works, WP7 support is still a work in progress. I think PhoneGap 1.7 makes it work slightly better, so try r90 and PhoneGap Build again (manually set it to 1.7 by clicking Edit if it isn't already), but I'd imagine it's still going to have some problems until some technical issues are sorted.

  • They should both be about equally fast, although because neither supports both platform yet you can only compare different devices, which of course makes it unfair. The real difference is how each platform does publishing. Ludei haven't yet sorted that out though, they're still working on their build system.

  • Please see how to report bugs. We need steps to reproduce etc. Have you also tried the latest beta (r89)?

  • Try adding 'For each Sprite' above the 'Sprite is overlapping Text' condition. 'Is overlapping' used to have a built-in for-each, but if you specifically need per-instance behavior you need to add it in again now.

  • Generally you are not allowed to do this without asking, and if you ask you'll either get no response or they'll say no. However that FAQ seems to say you can use it "for home, noncommercial and personal use only... provided, however, that you must include or maintain all copyright and other notices".

    I'd still recommend you simply use original content, but if you must, at least keep a "Some content Copyright (c) 2012 Blizzard" or whatever.

  • Congrats! Let us know how it goes!

  • The main engine has had all references to jQuery disabled when running in CocoonJS or directCanvas. It was a bit tricky, but on the whole it's only used for utilities, form controls, and controlling the canvas in the HTML page. They could all be worked around without jQuery in the wrappers (except form controls which are disabled and won't work at all). It's a pain, but necessary to get it working.

  • I don't believe anyone else is currently having any problems with PhoneGap Build - can you share the .capx you used? Can you also list all the third party plugins and behaviors you used? Some might not be compatible with PhoneGap.

  • Ludei are about to release an update for CocoonJS which hopefully will fix several issues that have come up.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • Please see how to report bugs. Can you describe in more detail the problem?

    Also, are you sure you haven't got 'snap to grid' on?

  • It's a known bug in Chrome 18. It's fixed for Chrome 19 already, so you'll just have to wait a couple of weeks or use the workaround Potato mentioned.

    This is a relatively serious bug and I was a bit annoyed they managed to let this get in to the stable release of the browser, but they wouldn't update Chrome 18 after it had already been released.

  • This is sort of by design... "Destroy" means "flag to be destroyed at the end of the event sheet". This is because people commonly write events like

    Destroy Sprite

    Create explosion at Sprite.X, Sprite.Y

    If the Sprite was really destroyed, the explosion would have nowhere to be created because the Sprite doesn't have an X or Y co-ordinate any more. I could fix the two cases you've shown, but the object would still actually exist until the end of the event sheet, which might just make for some more confusing cases.