Xander Wang

Hello @bberak, thanks for the swift reply. Here is a sample code on snack: https://snack.expo.io/@xdrawks/game-engine-vs-view-vs-touchablewithoutfeedback On iOS, the `Game Engine` and `View Surface` can be interacted independently from each other,...

Hello, looks like the snack is causing some confusion. Grey colouring does not indicate that it is actually pressed (`TouchableOpacity` might show a press on the UI side, but it...

Currently, I have a touchable game that uses the `GameEngine` and there are buttons outside the `GameEngine` component that assists in the game. Currently, I'm exploring if overlaying the `GameEngine`...

I realised in `GameEngine.js`, the current touch system relies on React Native's `View` component. I believe that's why it works perfectly with other independent `View` on iOS but not on...

Hmm, I'm not sure too. I think the main problem lies in the inconsistent `View` behaviour on both Android and iOS in React Native. I could image a new problem...

Hello @bberak, I just realised that my approach still doesn't work. While the `TouchableWithoutFeedback` component is pressed, any new touches to the `GameEngine` component are blocked 😞. Looks like I...

Hmm, it might not be elegant too, but let me think how to dispatch the touch callbacks from `GameEngine` to the buttons without having the buttons to exist as entities....

Hello @bberak, I’ve been working on the other parts of the game, so I haven’t work on a fix for the bug yet. I saw your solution, and I was...

Hello! Sorry for the delayed reply, was busy with other things as well. I eventually solved the touch problem by having a parent touch component `View` over the `GameEngine` that...

@bberak I didn't provide a new `touchProcessor` prop but actually wrote two components, a `TouchManager` that dispatches all the touch events via React context and callbacks to the `TouchView`s that...