A Pixi UX library seems to require manual render() frequently #5627
Unanswered
bingomanatee
asked this question in
Q&A
Replies: 1 comment
-
|
Pretty sure you have the wrong pixi repository. This is the repo for the package manager pixi. Seems like you are talking about https://pixijs.com. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I created a library for few things in pixi - buttons, windows, resizer handle array, dragging - and I try to enforce updates to happen inside tickers as in the past I got artifacts when I did not.
However in drag, if I do not call app.render() the storyboard demos "freeze" - as in I drag a handle and the widnow does not resize.
This is inconsistent; for instance the base resier storyboard does refresh even if I don't call render() myself, but the render utility used in windows (the same code) freezes unless I manually render() the app while I drag.
I did discusss this with codex/chatGPT and there are no obvious reasons the PIXI app would not pick up on the updates (position.set's as well as windows redrawing contant on drag) so I would like to know - all the docs suggest changing content on observable points or re-drawing graphics should definitiely cause pixi to re-render without manual rendering.
thoughts?
Beta Was this translation helpful? Give feedback.
All reactions