Best method to handle the software button bar?

Solar2D Android
#1

I’m busy converting my app to Android, and so far it has been pretty trouble free using the ultimate config.lua method. On devices that do not use software keys, everything looks fine, despite the 4:3 to 16:9 disparity.

However, with devices that use software keys (i.e.: Nexus 7) I’m seeing problems with what the app is doing versus what is showing on-screen. 

[lua]local temprect = display.newRect(0, 0, display.contentWidth, display.contentHeight)

temprect:setFillColor(0.5,0.5,0.5)

[/lua]

Using that bare code as an example, a rectangle is created that’s actually thinner (not as tall) as the available display space on the tablet once the button bar is subtracted (that is, there’s a gap on the bottom and top!) It’s distinctly noticeable on my device because I have sprites that are tall enough to stick above the gap.

Is there a different value I should be using instead of display.contentHeight? viewableContentHeight seems to provide the same value, and pixelHeight doesn’t seem useful in the ultimate config.lua scenario…

#2

display.actualContentWidth/Height should work for you :slight_smile:

  • C
#3

Thanks Caleb.

One minor fix though; by using display.actualContentWidth/Height, it seems to report values specific to the current orientation. So if you’re making a game using landscape, one must use the opposite variable that you might normally use.

#4

display.actualContentWidth/Height should work for you :slight_smile:

  • C
#5

Thanks Caleb.

One minor fix though; by using display.actualContentWidth/Height, it seems to report values specific to the current orientation. So if you’re making a game using landscape, one must use the opposite variable that you might normally use.