I just wanted to add that this happens even in a minimal haxeflixel template project.

If anyone could confirm this it would be great help.

At first I thought this was a hardware issue, but then I noticed that only my most recent game wasn't detecting touches near the top and bottom of the screen reliably (in landscape position). Other apps (including older games I made with HaxeFlixel) work fine. I am using HaxeFlixel 4.3.0, and have been testing on an iPhone 5s. This problem does not occur in the simulator, nor on Android devices.

Detailed characteristics of the problem:

• Taps near the longer edges of the screen are not detected by FlxG.mouse.pressed and FlxG.touches.list remains without entries.
• While no entry is created in FlxG.touches.list at the moment I tap near an edge, an entry is created when I release the tap, with FlxG.touches.list[0].pressed as false.
• The tap is detected near edges after I hold it for about 1 second.
• The taps near the edges are also detected (immediately) if I am holding another finger on the screen elsewhere (even near an edge).

Also, the game runs smoothly at 60 fps, so it is not a performance issue.

Any ideas of what could be causing this? Thanks in advance.

This is an old topic, but I just noticed that openfl.system.Capabilities.language doesn't show the country code along with the language. For example, it doesn't distinguish between Brazilian Portuguese (pt-BR) and European Portuguese (pt-PT); it returns "pt" in either case. Is there any way to get the country code or location as well?

@gama11 Awesome, I didn't realize there was a fix to this. It was easy to change and completely fixed the problem, thanks!

Since creating a substate doesn't pause the tweens, I'm wondering if there's a way to manually pause them, even if it's some dirty hack? I tried adding if (FlxG.state.subState != null) return; at the beginning of FlxTween.update() to see what happens, and while the tweens do seem to pause, they also "complete" while in the substate, as if they hadn't paused.

For me neither changing the stage quality nor setting fullscreen to false made any improvement.

I've noticed a graphic glitch when testing my game on a Sony Tablet S.

It's an old tablet from 2011, so it's not that important, but I'm afraid the glitch may appear on other devices.

Basically there's a strange fussy pixelated effect which is particularly noticeable on black lines which should be completely straight (image scaled 200%):

I've tried changing anti-aliasing on and off, but it doesn't make much of a difference.

I'm wondering if anyone here has seen this before or has a suggestion for fixing this? Thanks in advance.

When I return to my game after the device has gone into sleep mode (from either auto-sleep due to inactivity, or from pressing the power button), Android's navigation bar appears in the game, and does not go away. Interestingly, this does not happen if I exit the game and re-open it.

I want to use immersive mode and keep the game always fullscreen, but it seems that fullscreen is not maintained after sleep. Is there any way around this? Thanks in advance.

I'm just wondering if it's possible to make a sprite get hidden behind a fully transparent sprite (or rectangle). The sprite should be able to be only partially hidden behind the transparent sprite, creating an effect like this:

Is there a way to do this? For C++ targets.

I'm also having this problem and it's driving me crazy. I want the game to always use the same vertical resolution, then use the ratio of the screen to determine the horizontal resolution (in landscape mode). Then the game should be zoomed in/out to fit the full screen. Since the initial resolution from flash.Lib.current.stage.stageWidth is a little less than what it should be because of the Android navigation bar that auto-hides, the game has a thin black bar on the left and right sides of the screen. I then try to resize the game to full screen shortly after it starts (since the ratio will be correct then), but I've not been able to do this without breaking something.

The closest I've come to solving this is by first calling "FlxG.scaleMode = new StageSizeScaleMode();" shortly after the game starts, but then FlxG.width and FlxG.height will be wrong (with the screen resolution I think), so I hacked a way to change just FlxG.width and FlxG.height to the values of FlxG.camera.width and FlxG.camera.height (which for some reason are correct). FlxG.resizeGame() would not work like I wanted, the game would not be zoomed to fit the screen.

This seemed to work, but has an issue. If I quit the game via Android navigation bar, and open it again (so the game resumes), FlxG.width and FlxG.height will have the screen resolution dimensions, so the positioning of elements will be incorrect (since I use FlxG.width and FlxG.height to position things).