Results returned when using getDeviceWidth and getDeviceHeight on Androids

OZApps

I do not work much with Androids, but have to cater for Androids on and off. As far as I recollect with the Kindle Fire, though the resolution was 1024x600, part of the screen is covered with a system buttonBar that houses the buttons.

So my question is for those that work with various Android devices, on iOS getting the DeviceHeight and Width and subtracting the toolbarHeight would give the usable size of the screen. With Androids, does Gideros return the usable size of the actual size advertised?

I have some resizing code and want to make sure that if it checks for 1024x600 and the device returns 1024x560 then the code will fail. So any feedback on this??

ar2rsawseen

@OZApps unfortunately there is no easy answer to this one

With devices I've tried, the onscreen toolbar is not calculated in, thus you would have the 1024x560
but with the latest Android version, there is an immersion mode, which can be enabled and you will have full 1024x600

For as long as I know, then immersion can be enabled programmatically:
https://developer.android.com/training/system-ui/immersive.html

But maybe there will also be end user way to enable/disable it.

OZApps

Thanks for that @ar2rsawseen, however my question still is a bit simpler, what would the function return at the moment. Since I am hard coding for the values in the Gideros Player, I expect them to be the same, if the values are not returned as expected, the scaling, etc will not work, so I wanted to know what is returned by these functions in Gideros.

ar2rsawseen

Then getDeviceWidth/Height should return values without the onscreen buttons, as 1024x560

DisplayMetrics metrics = new DisplayMetrics(); this.getWindowManager().getDefaultDisplay().getMetrics(metrics); screenWidth = metrics.widthPixels; screenHeight = metrics.heightPixels;

OZApps

I tried this in Portrait Mode on a Samsung Galaxy Tab which has a resolution of 1024x600, but the return value is 976, this means that the soft toolbar is approximately 48 pixels. Is there a way to determine the height of this toolbar so that it can be added to the

application:getDeviceHeight()

to get the actual specified dimensions of the device screen.

working with the screen resolutions is easier than working with models and types, etc.

ar2rsawseen

There is a way to retrieve those in Android (although also tricky, because in different versions of Android it will work differently), but I don't think there is a way to do it in Gideros

OZApps

Reminds me of my love for Androids and Java...
Where all of the android hardware I spend my money on is unusable, where as all of the Apple hardware (iPod, iPad, iPhone) some of them are not usable for development now, but still function well as music players and phones or gaming pads. Where as the Androids are just battery guzzlers that switch off before you can do anything.

But just because a large majority of people afford and buy Androids, there is that voice of reason that suggests include Androids as a user base. While there are more users that purchase (with real money) on the Apple Store than on Google Play. So, why Androids???

My rant for the week....

keszegh

for me the return values are always the size of the useful screen (so it does not contain the status bar if there is one onscreen). so far it was consistent and ok for me, although i do not test on many devices, mostly one tablet and one phone.

OZApps

@keszegh, I have scaling multiples based on the screen resolutions. The issue is that if the multiples are incorrectly calculated, Gideros could have strange results. If we can get more information about the devices, we could back calculate the actual sizes based on screen size in inches and dpi, but then @Atilim could also offer us the actualSize or the HardwareScreenSize.

ar2rsawseen

@OZApps I can create a quick plugin returning real screen size with button bars, will it help?

OZApps

@ar2rsawseen, That would be wonderful, however if it is native (part of the next update) the code remains solid for a long time and does not rely on external code i.e. makes it more reliable and solid.

In the interim, I guess this would be a good idea, while I am also thinking of other alternatives.

It would still help to have functions that return the screen size in inches, dpi, etc

ar2rsawseen

I think this can be done in the release version, but we would need to understand the need and stretch it to crossplatform (as in think what these same methods will do on other platforms)

So let's start with what is needed.

For now you can retrieve dimensions in logical units using
application:getContentWidth/Height

Then you can get devices usable dimensions in pixels using
application:getDeviceWidth/Height

You can also get screen density (dpi) using:
application:getScreenDensity

So now here I might be a little lost in the units, but it means you can get inches by multiplying dpi with pixel quantity, right?

So the only thing that is needed is to get real dimensions with something as
application:getRealDeviceWidth/Height

Which on ios and desktop can return same deviceWidth/Height dimensions?

Does it make sense?