Never getting an ENDED touch?

toadkick · October 7, 2012, 1:00pm

I’ve opened a ticket for this in the issue tracker.

sim · October 7, 2012, 3:21pm

Thanks for opening the issue, so is this problem that touches are never getting into the ENDED or CANCELLED state?

Andrew_Stacey · October 7, 2012, 5:23pm

I must admit that I’ve never tested for CANCELLED.

toadkick · October 7, 2012, 6:46pm

I didn’t even know that CANCELLED was exposed…is it? AFAICT, the touch handlers never alert the Lua side that the touch was cancelled, so they are just kind of “lost”. Ideally the cancelled state would be exposed so that we can react accordingly. Non-ideally, at least and ENDED event could occur so that the touches aren’t lost.

sim · October 7, 2012, 7:16pm

CANCELLED should be exposed. It’s rare but occurs when the OS interrupts the touch handler.

toadkick · October 7, 2012, 7:37pm

Ok I see…while CANCELLED is in fact exposed, due to the problem I mentioned in the touch handlers in my comment above, the state of a touch that is cancelled never actually gets set to CANCELLED. Instead it appears that they are set to “inactive”.