Ashley's Forum Posts

  • The gaps probably appear due to sub-pixel rendering and your unusual control system. If the hotspot is centered and the object as an odd width/height, this makes the object edges land between pixels, e.g. a 5x5 object with a centered hotspot (at 2.5 x 2.5) placed at (10, 10) has its right edge at X = 12.5. Since Platform only works to the nearest pixel it leaves a half-pixel gap which can appear as a narrow space.

    Secondly why do you set the vector manually instead of using the control system? The Platform behavior wasn't designed to be controlled that way and it seems the push-out algorithm leaves a gap. If I set it back to default controls and disable your events it doesn't leave a gap. I'm not sure why it leaves a gap your way, but wouldn't it fix it to just use the behavior's control system?

    Still, for the next build I've increased the is-by-wall detection to 2px.

  • I'm afraid that adobe/Flash wins again

    Why? It looks like they've done a lot of work to rewrite their entire engine for iOS, which isn't using Flash at all.

    he developers over the world take ChromeApp not as real app, but just a link

    You're not required to host a Chrome App on a URL. You can make packaged apps which are not online and must be downloaded to be used. See Publishing to the Chrome Web Store for more information. You can still monetise public apps anyway - you can have the user log in and securely do in-app purchases, buy full version, etc.

    sincerely hope that C2 developers care more about mobile-devices.

    We do, we really do - we're keenly aware of the importance of mobile and monetisation, and we have lots of ideas for this - but we're a tiny 2-man team and the editor itself isn't even finished yet. We're trying to work through our todo list as fast as we can.

  • You really should not use layers for levels! Construct 2 is not at all designed for this to work, it's amazing if it works at all!

  • See How to use the System 'Wait' action. 'Wait' does not suspend the entire event sheet - it would really not be at all useful if it did. So the events carry on running as normal (e.g. loops finish instantly), it just schedules the rest of the event to be run after a delay.

    Usually what you really want to do is something like

    + For each Sprite

    -> Wait loopindex seconds

    -> Do something with Sprite

    This spreads out each iteration one second apart. If you do this:

    + For each Sprite

    -> Do something with Sprite

    -> Wait 1 second

    It means "run the loop instantly, wait 1 second, then do nothing".

  • Ah yeah, the Instance Variables dialog is a good place to folder organise it, but I'm not convinced by the UI to pick a folder. It would be better to have a dropdown treelist in the events, but I guess that might be a bit fiddly. I don't know, it's a nice idea but we have way too much on our todo list already, maybe I'll come back to it in future.

  • A built in 'else' condition has been on the todo list for a while, it's just got a low priority because it's easy to work around (copy the event and invert it) and the implementation is actually quite tricky (it must use the exact opposite picked objects from the previous event).

  • You do not have permission to view this post

  • Great work! Love the little minimap.

    The text selecting is a bug with having WebGL enabled, it should be fixed in the next build.

  • Email it to me to ashleywdf@scirra.com and I'll take a look. Please don't forget the steps to reproduce the problem! (Does task manager show it using way too much memory?)

  • You do not have permission to view this post

  • The project bar allows you to folder organise objects, but currently some dialogs (like new condition/action) still display everything without any folder organisation. It's on our todo list to get folders to display there, but it's a low priority since it's still pretty easy to quickly find objects via the search box.

    I'm not so sure about folder-organising variables - I don't see any obvious way to fit it in to the UI. Properties in the properties bar generally aren't drag-and-droppable like the project bar is, so the same method of right-click, making folders and dragging stuff in probably won't work in the properties bar. What would organising variables look like?

  • Sorry noise, I didn't mean to be patronizing. If I could better word my response, I would say that the manual lists a complete reference of all the features the object has, so if you don't see it listed there, it's not supported - there's nothing advanced or hidden away that isn't mentioned in the manual. I'll add some of your ideas to our todo list though so hopefully they'll be possible in future.

  • Should be fixed in next build!

  • Do you mean resizing in the layout view, or resizing in the image editor?

  • Oops, a typo in the source means the non-global Array object isn't destroyed at the end of the layout - so when you come back, there are 2 instances of the Array object! Fixed for next build.