Ashley's Forum Posts

  • Right now Classic is effectively retired. We have not yet made an official announcement to that end, but we probably will at some point. Everyone familiar with the move from Classic to C2 knows it was a ground-up rewrite with a modified feature set. I assumed everyone not familiar with the transition would be new users who would naturally pick the newer and better supported C2, so I'm curious as to why you would pick the older and unmaintained Classic instead. Maybe we should hurry up and officially retire it to avoid people expecting its features in C2.

  • If you can only pick from a list of existing functions, there needs to be some different way to create a new function. That makes it a little more complicated than just adding, say, a dropdown for existing layouts. It's on the todo list though.

  • Don't worry, I've been keeping a close eye on it. I wanted to include 0.5 with the stable update r126, but it was only (and still is at time of writing) a release candidate. That implies there's still some work to be done before the final version 0.5. I would be happy to ship that in a beta release, and will if it's still RC at the next beta, but for a stable update I would prefer not to take a risk on a not-quite-finished version.

  • It's difficult to run a forum. It's hard to strike a good balance between allowing open discussion on a wide range of topics, and not upsetting anyone. I hope you're not offended by this, and that nobody reading this thread is offended. However everyone should be aware that a very diverse audience visits this forum, and it would be nice to respect everyone's views. Remember you're calling this "Christian Game Developers", not "Game Developers Group For Everybody", which I do think implies some exclusivity even if you did not mean for it (the way I read it the title counts for more than the description). But on the other hand you should be free to run a special-interest group and tell people about it.

    So: I think we should just have one thread per interest, pointing out a separate community, so people of that interest know where they can go, whilst avoiding any one group having too much prominence on the forum (which might make some uncomfortable or feel excluded). I will apply this rule from now on to any kind of community which is aimed at a specific interest, so I hope you don't feel picked on. I know there is already only one thread so it might not seem like I needed to point that out, but I think it ended up needing explaining, so everyone who visits this forum appreciates we're trying to strike a balance.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Rhindon: just a heads up, we received a complaint about this thread. Topics like religion are highly emotive subjects. It might be best to keep discussion on these subjects to a minimum on our forums, not because there's anything wrong with it, but just to help our forums stay neutral and not a place where people come to talk about beliefs. I say "talk", but I'm sure you know how the topic often ends up being discussed online, and our intent is to avoid any disputes happening on our forums.

    Anyway, I don't think there's anything wrong with setting up a group for like-minded people and then telling people about it, but it might be best to keep it short and to the point so interested members can head over to your group and take up further discussion there. I hope you understand - our focus is for the forums to remain neutral.

  • fassFlash, consider this a warning. Please make sensible posts; it's not unreasonable that people find it odd you emphasised "excuse my english" so much, and it was totally redundant. Insulting people is outright against the rules. Please improve your conduct or we'll have to take further action.

  • Thanks, should be fixed in next build.

  • Thanks, this should be fixed in the next build.

  • Oops, you're right. Should be fixed in the next build.

  • ramones was right, there's a fairly complicated rule about newly created objects not being pickable until the next top-level event completes. This is deliberate, because the way the engine is architected, allowing this could cause crashes. So the problem is any condition in the function call cannot pick the newly created instance. However it's been reported enough now that I think it deserves a workaround specifically for 'pick by UID'. I've done this for the next build, and now 'pick by UID' can even pick instances that are freshly created. I tested the example and it seems to work now. So hopefully that makes creating objects with functions a lot more convenient!

  • ashesh - we just released r126, you'll now need to use that to submit to the Arcade.

  • It works with unique IDs each time on iOS. On Chrome for Android, the touch ID is always 0 for the first touch, and appears to go up to 1 for the second touch. This is perfectly correct behavior; the spec for touch events only requires the identifier be unique to all other active touches (because touch IDs are only useful for distinguishing simultaneous touches), so re-using a touch ID of 0 is perfectly valid. Since your events aren't really aware of multi-touch, it's hard to see this happening when you touch both sides at once, but the ID does go to 1.

  • Try using 'compare values' in the System object and comparing the playback time. (It ought to work without the Web Audio API...)

  • I think that's just the drag and drop behavior, which supports multi-touch.

  • The Touch object's accelerometer expressions work on Windows 8.

    The PlaybackTime expression ought to work even without the Web Audio API - can you share a .capx of how you're using it?