Migrating from v7 to v8 #9791
-
Hi! I am happy to see that Pixi keeps evolving. I realy liked new way of creating object in unified way, especially Text. I've been trying to port my app to v8. And now I have some difficulties with this process. I want to highlight this so that you could address it in future releases. Also if I mistakenly understand something, hope you will direct me.
|
Beta Was this translation helpful? Give feedback.
Replies: 8 comments 20 replies
-
TextI have couple questions regarding new Text implementation:
|
Beta Was this translation helpful? Give feedback.
-
Pixi PlaygroundI think I encountered few bugs in v8, but Pixi Playground seems broken for 8.0.0, so that I couldn't make reproducible example to report these bugs. By default it opens example for 5.3.0, but if you switch to 8.0.0, it couldn't fetch types, and source of default example doesn't fit new async init procedure. Ok, maybe, if I write some async code by my self it would work, but it's unclear how I should access pixi apis. Is there still PIXI god object, or I should import it. I dont know. For now it's just hard to provide examples of broken behaviour, because playground little bit outdated for now. |
Beta Was this translation helpful? Give feedback.
-
New Graphics -
|
Beta Was this translation helpful? Give feedback.
-
New Graphics -
|
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Pixi DevTools extension for ChromeWhat works:
What doesn't:
|
Beta Was this translation helpful? Give feedback.
-
Thanks so much for such detailed feedback and questions! Will get back to you shortly 👍 |
Beta Was this translation helpful? Give feedback.
-
Misc / Other
|
Beta Was this translation helpful? Give feedback.
Tested today with beta8. Memmory issue gone! And all other related to missing strokes and fills. Looks like all issues discussed here has been resolved. 🎉
Thank you very much!