Android touch issue after update SDL from 2.0.1 to 2.0.8

White_Dragon · April 3, 2018, 4:15pm

I noticed a touch input issue on this project:

It seems that the touch is not detected in all frames… Like a lag…
Then I noticed that this problem is not present if the screen is stretched (and it fills the whole screen).
It can be depend by the blend mode? Or by touching screen point with no texture? Can you help me?

files:

github.com

DCurrent/openbor/blob/master/engine/android/jni/openbor/video.c

/*
 * OpenBOR - http://www.chronocrash.com
 * -----------------------------------------------------------------------
 * All rights reserved, see LICENSE in OpenBOR root for details.
 *
 * Copyright (c) 2004 - 2015 OpenBOR Team
 *
 * Video.c - adjunct to the main build's video.c.
 * Made by UTunnels (utunnels@hotmail.com).
 * Modifications by CRxTRDude, White Dragon and msmalik681.
 */

#include <math.h>
#include "types.h"
#include "video.h"
#include "vga.h"
#include "screen.h"
#include "sdlport.h"
#include "openbor.h"
#include "gfxtypes.h"

This file has been truncated. show original

github.com

DCurrent/openbor/blob/master/engine/sdl/control.c

/*
 * OpenBOR - http://www.chronocrash.com
 * -----------------------------------------------------------------------
 * All rights reserved, see LICENSE in OpenBOR root for details.
 *
 * Copyright (c) 2004 - 2014 OpenBOR Team
 */

// Generic control stuff (keyboard+joystick)

#include "video.h"
#include "globals.h"
#include "control.h"
#include "stristr.h"
#include "sblaster.h"
#include "joysticks.h"
#include "openbor.h"

#define T_AXIS 7000

This file has been truncated. show original

White_Dragon · April 3, 2018, 8:09pm

Maybe there is an input issue on touch out of first layer texture?
This is a SDL2 bug I think… please help…
Tested with API from 14 to 22.

Edit: I tried to create a texture and I placed it under all texture as a “texture base”.
Now the touch is detected better… but it doesn’t work properly… Why?
Edit2: it seems to be a ghost touch (wrong screen position touch) ex.: i i touch upper/left at random time it seems to touch the bottom/right screen for example…

touchId can be useful?

White_Dragon · April 5, 2018, 9:30pm

I noticed that event.tfinger.x and y return negative value…
doc tells that them retur a value 0…1
is it a bug? it’s strange…

White_Dragon · April 11, 2018, 10:05am

Any help?
Please I can’t fix this bug…

AntTheAlchemist · April 12, 2018, 1:47pm

Something like this happened to me when I used SDL_SetRelativeMouseMode(). Android doesn’t support this feature, so it produces this bug. Not sure if this is the case for you though. I’m struggling to get SDL2 working under Android Studio, so I can’t test it.

White_Dragon · April 12, 2018, 6:14pm

I don’t use SDL_SetRelativeMouseMode() but thanks…

White_Dragon · April 13, 2018, 8:40pm

Not resolved…
I really have no idea!

White_Dragon · April 16, 2018, 10:46pm

maybe the issue / bug is related to SDL_RenderSetLogicalSize().
it SDL_FINGERDOWN/SDL_FINGERUP/SDL_FINGERMOTION etc. return wrong (and/or negative) touch input positions…

White_Dragon · April 21, 2018, 4:30am

ok, there is a bug with SDL_RenderSetLogicalSize()
used SDL_RenderCopy(renderer, texture, NULL, &d_rect); for now…

AntTheAlchemist · April 21, 2018, 12:30pm

Nice find. If you can reproduce the bug using a simple test.c, then post the bug on https://bugzilla.libsdl.org/ and someone there will fix it.

Not many people here are using Android in much depth, which is why you haven’t got a reply. I’m using it extensively, but I’ve not used LogicalSize yet… but I will soon.