David Figatner

Ideally this can be fixed by adding an optional second boundary to `mouseEdges` that provides an outside boundary for the `mouseEdges` hittest. Would that help?

Hmm...yup, it's likely caused by my fix to the types for v6. I don't normally use typescript, so if you could suggest a change to the types that would work...

Thanks!

You need to move the `gridTillingSprite` with the viewport so it's always visible. You can attach to the `moved` event and then do the math so the sprite is in...

I'm afraid that's the current behavior. I've not added rotation support to the viewport. There are some calculations that will likely be broken when using a rotated viewport (although rotated...

If you mean rotating the entire viewport to match the target's rotation, then, yes, this is not available. The actual rotation of the viewport itself shouldn't be too difficult. The...

Hmm...that is weird. PIXI.Application includes a default stage, but there shouldn't be any parent above that. I'm not sure how visible would be set to false as I don't think...

If you remember, please let me know which parts of the documentation were not clear. I've added a lot of features over time, and I know some of it is...

Phew. It turns out I did code the viewport for axis independence (it's amazing how quickly I forget what I did). But there were bugs in both wheel() (which was...

The viewport is based on pixi.display, which handles x and y scale independently. Many of the viewport's plugins (like pinch and wheel) are not designed for independent zooms (mostly because...