I have the 12.9" iPad Pro if you need that
You can confirm on this project that multiplying by 341 gives a whole number no matter the last touch Y horizontally (and 1 for vertical)
The number pointed to should be 341 for landscape and 1 for portrait, and they should always give you a whole number when finger moves.
How come this post got 8 likes? I’m a bit curious, it wasn’t any special.
I dunno, maybe it’s just on my topic and that you provide a good resource…
This goes in #meta-hopscotch @TheCMStudios
“Custom UI Button” Placement Testing. Like Minigames 2 but with modifications
First custom at (782, 736)
Sound button placed at (838, 736)
Difference of 56 in x.
in descending order,
[782, 726, 670, 614, 558]
(144, 736)
(88, 736)
Difference of 56, as expected:
[144, 200, 256, 312, 368]
This will be implemented into my HHC19 project. If on an 9.7" iPad (2, 3, 4, Air [2013], Air 2, 2017, 2018), the in-game options will be placed by the UI. If not, it will show up by your inventory.
Size 64 invis 47, pressed invis = 84
427 / 332
Firefox wow…
this whole thing needs reworking.
332… ok
@TheModders – could have also posted this in HS help guide topic, but it had to do more with specific device results. Not the same as in-app last touch-based guessing, but rather just platform.
Latest Collision Test:
DeviceTestAlpha7
Much faster version:
DeviceTestAlpha8
Direct HS Link:
(note that results in my reference for web browser are based on my GitHub page. I may also include a result for broken emojis such as the gear, or maybe an update will roll out where the emoji issue gets fixed)
yes
yes
(Trying to update my Device ID Reference due to some inaccuracies and inconsistencies)
@TheModders could you test this project on the following iOS versions if you have any of them?
- iOS 10.2.x in HS App and browser
- iOS 10.0-10.1.x in App and browser
- iOS 9.x in App and browser
After 1st restart, reply with iOS version (Settings/About/Version) and one of the following:
- The numbers of the collision
- “Project did not load”
- “Square did not render”
- “Text did not render”
(collision did not occur means you did not run on 1st restart)
If you don’t have them, I could also use a Chrome OS screenshot.
bump
Now that the New Edge browser was pushed out, I tested its JS and emoji/text rendering.
Edge 81:
Chrome 83:
Emoji/text rendering:
(using this)
Same as Chrome – 417 / 304
Since Edge is now built on Chromium, its JavaScript performance is much better, and it will identify as a Chromium-based browser.
The new Microsoft Edge has been around for a pretty long time
I know, but my computer’s manufacturer is one that applies their own changes to every Windows update, and as a result delay releases.