Ashley's Recent Forum Activity

  • Closing as is same underlying issue as https://www.scirra.com/forum/undo-removes-wrong-action_t179505

  • I can't reproduce any issue in Chrome for Android (currently v52) - the debugger is fiddly on mobile so I just added a text object showing the duration and playback time (.capx: https://dl.dropboxusercontent.com/u/15217362/sound_music_bug_2016_08_31.capx) and it displays the correct duration and playback position.

    I know that Google have been doing some heavy work on the audio engine in Chrome for Android recently, and v52 made some big changes, so maybe check your Chrome is up to date and try again. If not try Chrome Dev for Android which is newer. I think you were seeing a problem on an older version that was subsequently fixed, so closing this report.

  • Should be fixed in the next build.

  • Timers never interrupt anything - in fact no events ever interrupt each other, they are queued to run synchronously with other events. I just meant if you use something like "call function", that jumps away to another event, runs it then comes back, by design.

  • I can't reproduce the issue on iOS. In Safari it just shifts all the content up above the keyboard so you can always see the same content regardless of if the keyboard is open or not.

    There is a problem in Chrome for Android, but it's not really a C2 bug, it's just an unfortunate consequence of the way Chrome handles the on-screen keyboard: when the keyboard comes up it actually fires resize events and causes the window size to change so it's reduced to just the area above the keyboard. Due to the fact you use "scale inner", this causes the aspect ratio to change, and then some text fields go off-screen so are hidden, and that causes the keyboard to be hidden if you tapped one of those text fields.

    If you use letterbox mode it just scales down the entire view which keeps all the text fields on-screen and works OK. So really this is just a consequence of how Android handles bringing up the keyboard combined with the fullscreen mode you've chosen. It's similar to this bug, which Google are aware of and they plan to fix the keyboard to work like Safari to resolve issues like this. I assume it's a similar story on Windows Phone.

    So closing as won't fix since it needs browser changes to work around. Alternatively you can just use letterbox scale.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I can reproduce, but it's a problem with the runtime architecture: triggers fire on object instances, not behaviors, so either behavior can trigger a general "On shoot" condition, which doesn't distinguish between each behavior's triggers.

    I think this was reported in another bug a while ago.

    I'll leave this report open but given that architectural changes are needed I don't think this is something we'll fix before C3.

  • Yeah the real problem is you're circumventing the type check using a global variable to pass a number where you should pass a string.

    Ideally C2 would reject this as an invalid expression but then changing the type of global variables could invalidate large numbers of expressions. That's not such a nice consequence. So closing as won't fix.

  • Closing as duplicate of https://www.scirra.com/forum/sound-issue_t180275

    tl;dr - it's a Chrome bug which is already fixed.

  • Closing as 99Instances2Go is right, the return value is set by the last completing function, it does not access the current function's return value.

  • I'll close this report since my numbers indicate it resolves the memory buildup, and the change is in the next build as well, so I guess file a new issue if you still have trouble.

  • Yeah, this is more of a feature request - the runtime is not really designed to change the fullscreen mode at runtime and the Browser object's action is not really meant to be a way to alter the project setting. Nor do I think it's sensible to use this approach to work better with a keyboard - going fullscreen tends to hide any other UI, which could include hiding the keyboard the user just tried to bring up...

    I'm going to close this report in favour of the feature request that TheRealDannyyy made.

  • Intel graphics are crap, but a bit less crap than they used to be. I think it will be OK without a dedicated GPU on modern hardware. Dedicated GPUs are much better, but they tend to only come with more expensive laptops.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,777,181 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x42
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs