Comments (4)
this PR seems to be the cause of this: #9474
from pixijs.
After more investigation, it seems like the events that can be listened to are the elements from the touches
array, but somehow the original value of the property identifier
gets lost by the time the event gets to the registered event handlers. If it didnt get lost, it would be possible to reconstruct the TouchEvent
from the multiple events it gets split into
from pixijs.
I'm not sure what the problem was yesterday, but today the identifier
property is working correctly again, making it possible to get touch functionality. Splitting up the touch events by entries in the touches
array still isn't optimal, as the array needs to be manually reconstructed to properly handle multitouch gestures.
As there are still usecases in which splitting these events by touches
is useful, I suggest adding a new set of multi-touch specific events that include the entire touches
array
from pixijs.
is there any workaround for this?
from pixijs.
Related Issues (20)
- Bug: [v8 regression] pointerevents can drastically cut performance HOT 2
- Is there a way to simulate 3d projection/rotation in Pixi v8
- Bug: [v8.0.2] Sprite not updated correctly when its texture's frame is changed HOT 2
- Bug: [v8 regression] `Container.destroy()` is very slow on crowded containers HOT 5
- Bug: Publishing v7.x doesn't update latest dist-tags
- Bug: [v8 regression] moving a crowded `Container` drastically cuts performance HOT 8
- Bug: [v8] When adding `onRender` to a class extension, it does not work as expected
- Feature Request: [v8] Is there any way to pass a canvas instance to the new WebGLRenderer? HOT 2
- Bug: export image empty on firefox
- Bug: v8 Using webcam stream as source errors in Chrome HOT 3
- Bug: [v8] passing `fill(0)` or `fill(0x000000)` to graphics shows white instead of black
- [v8] Cannot read property 'addRenderable' of undefined HOT 4
- Bug: [v8] The filter is not taking the RenderTexture's frame's offset into account when being applied HOT 1
- Bug: Fill hex for black produces unpredictable results HOT 1
- Bug: Could not render app.canvas to normal canvas correctly in Windows chrome HOT 1
- Bug: roundPixels=true causing precision issues HOT 2
- [V8] Error with `new Sprite(null)` HOT 2
- Bug: v8.x Sprites not rendering in Chrome/Edge Windows 11 HOT 5
- Bug: [V8] Container.removeChildren performance issue HOT 2
- Bug: `loadTextures` ignores provided format HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pixijs.