-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Transformer v3.0.1 seems broken #84
Comments
Hey Team , great work with upgrading the V7, specially the pixi-transformer. I was long waiting for that.. Seems like all the Events are null for the transformer object. |
The React helper package wasn’t designed for the new @pixi/react package. I would be happy to accept a PR that makes it work with the latest version (@pixi/react) |
@pixi/react is pretty much has the same API as @inlet/pixi-react. The package name changed because Pixi team took over the project. It was made compatible with Pixi 7 and React 18 in the process. I copied the code from react-bindings package and just switched @inlet/pixi-react references with @pixi/react and it seemed to work for me. Got some peer dependency warnings tho so would probably be breaking change to react-bindings package since React version would have to be updated from 16 to 18. Not sure about this codepen tho since it uses custom way to bind the Transformer while the usual way is to use PixiComponent utility from @pixi/react (docs: https://pixijs.io/pixi-react/custom-component/) which react-bindings package also uses to create Transformer. |
Hey @SampsaKaskela , thank you for the update, wonder if you would be able to raise the PR for the react-bindings? |
@khanzzirfan Just opened PR #91 although not sure how versioning should be handled there. Probably breaking change. |
Hi, just checking if this was fixed. That PR was merged. |
The controls are being displayed but I cannot interact with them, even on hover the cursor wouldn't change. I tried it with all kinds of settings. The same code works perfectly with v3.0.0
The text was updated successfully, but these errors were encountered: