Hello!
I am currently playing with HTML5 builds and found that when I build with Scale Mode set to Stretch I start receiving wrong input coordinates.
Not sure what information would be helpful so I’ll write evverything.
My setup:
- Windows 10
- Primary display scale 175%. Second deisplay scale 125%
- Application created from Mobile game template
- background image scale changed from 1.0 to 5.0
- game.project display width 1280 height 1024
- game.project html5 scale mode set to stetch
- html5 build is tested in Google Chrome
- Google Chrome window in position 350,40. Widnows ize 4744×2047. Developer console is visible to the right with width 1245
Then I click on the most bottom down “dot” visible on the background image in fit mode. Without changing mouse position I am alt-tabing to window with application with stretch mode and click again.
touch event reported with scaling fit:
DEBUG: [defold-pos-rep] touch: {repeated: true, released: false, screen_dy: 0, screen_dx: 0, y: 34.890686035156, x: 1206.1538085938, screen_y: 64, screen_x: 2229, value: 1, dy: 0, dx: 0, pressed: true} <main/main.script:11>
touch event reported with scaling stretch:
DEBUG: [defold-pos-rep] touch: {repeated: true, released: false, screen_dy: 0, screen_dx: 0, y: 37.015319824219, x: 1023.7424926758, screen_y: 68, screen_x: 2782, value: 1, dy: 0, dx: 0, pressed: true} <main/main.script:11>
As you can see x position is different. Position reported in fit mode is correct from the game point of view.
Is it expected behaviour? If yes, perhaps someone will give me advice. My end goal is to let user see more of the backgroud instead of just cropped game area if their display is larger than game.
defold-pos-repro.zip (836.3 KB)