native.newText field position issues

Beta Testing HTML5
#1

Hi,

I have an app that is set for landscapeRight, but the text field is waaay off to the side of the screen. If I try portrait it still is offset in the wrong place.

I’ve tried it in a group and out. This is using composer scenes and does not have any window adjustments in the build.settings.

Is this a known behavior at this time?

Web landscapeRight

Web portrait

Device (what it should look like)

config.lua

application = { content = { width = 640, height = 960, scale = "letterbox", fps = 30, }, }

macOS 10.13.4

Chrome 66

Build 3238 3282

-dev

#2

Interesting. I thought we just fixed the text positioning in 3280.  Have you tried a newer version?

Rob

#3

Hi,

I must have went dyslexic on my build number, that should be build 3282, which appears to be the latest version.

I thought I read it had been fixed recently, but it appears something is still off.

-dev

#4

Any way to put together a sample project? It would help speed up things with Engineering.

Rob

#5

Hi,

Sure, the project itself is fairly large, so I’ll need to strip it down to the basics, but I can do that.

-dev

#6

We probably just need an example that shows the fields getting messed up.

Rob

#7

Hi,

Here is a sample project demonstrating the issue. It needs to be built for HTML5 first, obviously.

-dev

#8

Hi,

Was there any outcome regarding this issue? Or is it something I am doing incorrectly?

-dev

#9

I don’t believe this has been resolved yet.

Rob

#10

Native display object position issues fix will come with next daily build.

#11

Interesting. I thought we just fixed the text positioning in 3280.  Have you tried a newer version?

Rob

#12

Hi,

I must have went dyslexic on my build number, that should be build 3282, which appears to be the latest version.

I thought I read it had been fixed recently, but it appears something is still off.

-dev

#13

Any way to put together a sample project? It would help speed up things with Engineering.

Rob

#14

Hi,

Sure, the project itself is fairly large, so I’ll need to strip it down to the basics, but I can do that.

-dev

#15

We probably just need an example that shows the fields getting messed up.

Rob

#16

Hi,

Here is a sample project demonstrating the issue. It needs to be built for HTML5 first, obviously.

-dev

#17

Hi,

Was there any outcome regarding this issue? Or is it something I am doing incorrectly?

-dev

#18

I don’t believe this has been resolved yet.

Rob

#19

Native display object position issues fix will come with next daily build.