coronaWindowMovesWhenKeyboardAppears issue.

Solar2D Android
#1

Version: Corona-3208 (Native Android)

Issue: I use ‘<meta-data android:name=“coronaWindowMovesWhenKeyboardAppears” android:value=“true”/>’ like below.

\<manifest \<application \<activity android:name="com.ansca.corona.CoronaActivity" android:screenOrientation="portrait" android:configChanges="keyboard|keyboardHidden|navigation|screenSize|orientation" android:label="@string/app\_name" android:launchMode="singleTask" android:theme="@android:style/Theme.NoTitleBar.Fullscreen"\> \<meta-data android:name="coronaWindowMovesWhenKeyboardAppears" android:value="true"/\> \<intent-filter\> \<action android:name="android.intent.action.MAIN" /\> \<category android:name="android.intent.category.LAUNCHER" /\> \</intent-filter\> \</activity\>

And main.lua

display.setDefault( "anchorX", 0 ) display.setDefault( "anchorY", 0 ) local r = display.newRect(0, 0, display.actualContentWidth, display.actualContentHeight) r:setFillColor(1, 0, 0) display.setStatusBar( display.DefaultStatusBar ) timer.performWithDelay(3000, function () display.setStatusBar( display.HiddenStatusBar ) timer.performWithDelay(1000, function () display.setStatusBar( display.DefaultStatusBar ) end, 1) end, 1)

Corona View changes ugly. Would you test it?

#2

Corona-3220 is the same.

#3

Config.lua

local w, h = display.pixelWidth, display.pixelHeight local normalW, normalH = (w / h \>= 0.6) and 640 or 540, 960 local scale = math.max(normalW / w, normalH / h) w, h = w \* scale, h \* scale application = { content = { width = w, height = h, scale = 'letterbox', audioPlayFrequency = 44100, fps = 60, xAlign = "left", yAlign = "top", imageSuffix = { ['@2x'] = 1.1, ['@4x'] = 2.1 } }, }
#4

If you have the ‘Galaxy S8+’ device, you can test the ‘native.newTextField()’.

When you tap the textField, corona view changes ugly.

I guess, the device has unique right area.

So, horizontal size of corona view changes small.

Thank you. :slight_smile:

#5

You should consider filing a bug report for this that is: create a .zip file with a full project in it including main.lua, config.lua, the Android Studio project and any other needed files and then submit the bug report using the “Report a bug” link at the top of the page.

Now that said, “coronaWindowMovesWhenKeyboardAppears” is an experimental feature that we never certified as being 100% functional. As far as I know that’s a build.settings key for Simulator builds. I’m not sure it will work with native builds.  Because this is an experimental feature, I’m not sure what support Engineering will provide, but our engineers may have some native suggestions on how to use this feature.

Rob

#6

OK. I’ve done to submit bug report.

Thank you. (-:

#7

Corona-3220 is the same.

#8

Config.lua

local w, h = display.pixelWidth, display.pixelHeight local normalW, normalH = (w / h \>= 0.6) and 640 or 540, 960 local scale = math.max(normalW / w, normalH / h) w, h = w \* scale, h \* scale application = { content = { width = w, height = h, scale = 'letterbox', audioPlayFrequency = 44100, fps = 60, xAlign = "left", yAlign = "top", imageSuffix = { ['@2x'] = 1.1, ['@4x'] = 2.1 } }, }
#9

If you have the ‘Galaxy S8+’ device, you can test the ‘native.newTextField()’.

When you tap the textField, corona view changes ugly.

I guess, the device has unique right area.

So, horizontal size of corona view changes small.

Thank you. :slight_smile:

#10

You should consider filing a bug report for this that is: create a .zip file with a full project in it including main.lua, config.lua, the Android Studio project and any other needed files and then submit the bug report using the “Report a bug” link at the top of the page.

Now that said, “coronaWindowMovesWhenKeyboardAppears” is an experimental feature that we never certified as being 100% functional. As far as I know that’s a build.settings key for Simulator builds. I’m not sure it will work with native builds.  Because this is an experimental feature, I’m not sure what support Engineering will provide, but our engineers may have some native suggestions on how to use this feature.

Rob

#11

OK. I’ve done to submit bug report.

Thank you. (-: