David Figatner

Thanks. Added in v4.22.2.

Did you play with drag.options.wheelScroll and make it < 1? That's the number of pixels to scroll with each mouse spin.

Yes, I think I understand what you're asking. What's the user scenario for this? If a user wants to go crazy with spinning their mouse wheel, why slow them down?

Ah, I understand. I'm not sure it makes sense as an option on the drag plugin, however. The fastest way to do this is to create a user plugin based...

I remember the discussion below. What type of perf improvements are you getting with this? If I understand it correctly, you exchange the children’s local matrix recalculations for a single...

Oooh, now that I think about it, if we derive `Viewport` from `DisplayObject` instead of `Container` we can fix the children issue and have no breakage for the API users....

Cool. Then it's worth doing. The advantage to overriding the `DisplayObject` is that you can directly access `viewport.children`. I don't think there's a way of doing that if you derive...

No problem. We'll hold off on merging this to master until pixi releases its new version, and then add a minimum pixi version once it's released.

There is a rudimentary implementation of 2-finger panning. Right now, it doesn't work if you also use the wheel() plugin. I have code in the (I think) `gesture` branch that...

Yes, i finally have a nice mac to develop on. Let me see if I can get this implemented and figure out how this makes sense.