Sprite does not receive touch events when created outside of the visible area and then moved inside.

kussakov

I have menus and "drawers" that are build and attached to the scene three outside of the visible area. Then on some user action the menu glides in the visible area. After upgrading Gideros the menu item sprites stopped receiving touch events. I have been using this code for 9 years and now none of my menus and drawers are working.

If I create the menu inside of the visible area - the touches work.

I guess there is an easy fix for that, but can't figure it out.

Please help.

DESTAILS:
After a few years I decided to upgrade Gideros from 2021 to the latest version (2023.6).
All my projects stopped working (due to luau, module def changes, "bit" removed, etc).
It took me a day or two to revive one of the projects, but I have issues I can't resolve. Such as the one above and Android back button KEY_UP event not firing while KEY_DOWN is firing fine.

kussakov

One more test: When I create the slide menu to be initially "half visible" (half of the buttons are in the visible area and half outside) only half of the buttons receive touches when I slide the menu to be fully visible.

I use GTween to move the slider in visible position.

hgy29

I had a quick look at the code, I thought it could be caused by 'set()' call used by GTween not properly updated with the various changes, but no they look ok. Any chance you could send me a small test project that exhibits the issue ? I'll try to test on my side with debugger, but rewriting it my way I could compltely avoid what causes the issue.

kussakov

@hgy29 It could very well be related to set() used by GTween.
After reading your comment I did another test: Instead of using GTween for the slide effect I just did setPosition on the main slider. This time all touches work. This is now my workaround (to loose the slide effect while we figure it out).
I will try to write a sample project, but there is too much code involved and I have to simplify it...

EDIT:
Maybe not. I just did another test:

-- in GTween replaced this: self.target:set(n, val)   -- With this: if n == "x" then self.target:setPosition(val, self.target:getY()) -- self.target:setX(val) elseif n == "y" then self.target:setPosition(self.target:getX(), val) -- self.target:setY(val) else self.target:set(n, val) end

Still does not work. Must be something else GTween is doing... will keep digging.

keszegh

@kussakov , i encourage you to send your whole code to @hgy29 in a pm, i did this in the past many times and he always found the issue much faster this way. and i'm completely sure that your code is safe with him (and he will delete it afterwards if you ask him), as proven by my experience. but of course it's just an option that i recommend.

hgy29

@kussakov, any news on this ? I didn't manage to reproduce it, and couldn't find an obvious issue in Gideros code.

hgy29

Thinking of it, it may well be the same issue as https://forum.gideros.rocks/discussion/8696/changed-behavior-of-sprite-hittestpoint-without-a-fourth-argument