Ashley's Forum Posts

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Just use an inverted "cursor is over" event to put them back. That's effectively a picking 'else' condition.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  The .capx uses a third-party addon 'Trace' so closing, please see the bug report requirements. It is always useful if you can produce a minimal .capx with nothing else in it other than demonstrating the issue.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Thanks, should be fixed in the next build.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Thanks, should be fixed in next build.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Closing as not a bug: you're expecting 'else' to pick instances, but it does not. 'Else' simply means 'the previous event did not run'. It's possible to move the mouse over multiple different instances (since the mouse actually moves in steps, rather than smoothly, it can cross the gap easily) without the event ever being false. In this case the else event never runs even though the cursor is over a new object. The else event does not run until the mouse is not over any instances at all.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Closing as won't fix: creating an object with a drag-and-drop behavior on a touch start is not a reliable thing to do - the drag&drop behavior listens for touch events, but by the time you create it the touch event has already fired. I'm surprised this ever works in any circumstance, I'd expect it to never drag when you create an object in a touch event. I don't think it's reasonable to expect objects to catch events that have already started firing. This should be reasonably straightforward to implement via events anyway.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Does this reproduce in Chrome for Android in the browser? We ask that you test as many platforms as possible in the bug report requirements to help isolate what is faulty. If it works in Chrome for Android, I'd guess it's an issue with the Cordova plugin or the Intel XDK.

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Thanks Aphrodite for the minimal repro. Should be fixed in the next build.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Definitely, old and buggy graphics drivers are the #1 cause of glitches and crashes in C2.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  That context is private to the Text object, you shouldn't mess with it. IIRC it creates its own 2D context, even in WebGL mode, for text rendering.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  Start with the multiplayer tutorial which will probably answer most of your questions.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 21 Dec, 2016
  • Quote

  According to that bug report, it was fixed in 0.18.0+. I tested it and it seems to work OK in 0.19.2. If you still have issues please post to the nwjs report.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 20 Dec, 2016
  • Quote

  I think the slow thing is just the text layout. If you set the snapshot URL to a text instance variable, for example, it's perfectly fast. The slow thing is running text layout (word wrap etc.) on a huge block of unnatural text. I'm not sure there's much we can do about that. One easy workaround is just to display the first 300 characters or something if you want to show it to the user.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 20 Dec, 2016
  • Quote

  Think this is an NW.js bug: https://github.com/nwjs/nw.js/issues/5337

  I added a comment to that existing report - will follow it up there and close this report.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,105 posts
  • 1

  • 20 Dec, 2016
  • Quote

  Closing as duplicate report, should be fixed in next build now.