Touch Events and Retina Display

0 favourites
  • 4 posts
From the Asset Store
14 amazing sound files of game events like Level Ups, Level Completes, object spawn, object taking etc.
  • Hi. I'm not sure if this should be a Bug Report or if it should just be a question in the Forum. But I read Ashleys answer to bjadams post on this issue Touch Event and the iPad where he stated that "Touch events should work correctly with any settings." Well, it dosn't, for me at least, so here's my problem.

    On iPad 4, with Retina Display set to "On" the hitpoint for the Touch Event seem to be placed halfway from the upper left corner of the canvas in relation to the origin of the sprite button. I have tested with both Chrome and Safari on iPad 4, iOS6. This is not the case on a desktop (tested on IE9, Chrome)or on a Samsung GT-P5110 running Android 4 (tested with default browser). So the trouble is with the Retina Display in Safari on iPad4 on iOS6 (at least). It seems to me that I'm better off with the turning the Retina Display off, but I know nothing about any other consequences of doing it. This is a small case test after all, and turning the Retina Display off might affect the graphics on some other level?

    I made to different testprojects: RetinaDisplayOn.capx and RetinaDisplayOff.capx.

    Here is the exported html for each: RetinaDisplayOn/index.html and RetinaDisplayOff/index.html

    <img src="smileys/smiley1.gif" border="0" align="middle">

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • SigmundO

    I had the same problem.

    Here is a simple capx which is a cursor sprite.

    And here is a exported demo, which works well at pc and android. But had a problem at new iPad -- the sprite could not move at touch point.

  • Yup, big trouble on Retina - on both iPad 2 and (the-new-one-that-Apple-won't-call) iPad 3.

  • Thanks, should be fixed in the next build. Note it works correctly when using a fullscreen-in-browser setting; this bug only happens on the iPad 3 (iPad 4 is not out yet!) when not using a fullscreen setting.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)