You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The version check needs to be >= instead of indexOf(), or none of the 2.4 patches are activated. I had submitted a pull request to patch this, but then discovered the other problems and closed it pending more fixes.
The EZGUI.utils.isMasked() function searches all the way to the root of the tree for a worldTransform and never finds one for any event, ever.
Dragging doesn't respect screen scale. This is also true at least as far back as Phaser 2.4.8. EZGUI.utils.getRealPos() needs to use an inverse of the scale calculation found in isMasked(). I don't know if this is a new problem, but it's Yet Another Issue with Phaser.
Please at least let me know what a likely timeline is for fixes. It's fine if the answer is "when I get a chance," but if you can give a ballpark estimate then I'll be able to plan around it -- whether it's likely to be fixed next week or next year or somewhere in between.
The text was updated successfully, but these errors were encountered:
I've decided to give up on EZGUI and write my own system. Too many problems and bugs in too short a period of time, and no clear path to seeing them fixed. Sorry.
I've already implemented a mini-GUI system based on https://github.com/facebook/css-layout for layout that handles the basics that I need so far (creating images, styled text, groups, and Phaser.Button objects where the css-layout specifies object positions and scales). Eventually I'll need to create custom controls, but now that I have the infrastructure laid out it shouldn't be hard. And I'll get my scale9 support built in to the engine; I already put the hooks in place.
It also shouldn't be hard to abstract out the rendering layer after I create custom controls, so that I can support PIXI 3 and other renderers as well. Eventually. Creating game engines is kind of a habit of mine, so I guess it was inevitable that it would come to this... :)
Issues I've seen so far:
Please at least let me know what a likely timeline is for fixes. It's fine if the answer is "when I get a chance," but if you can give a ballpark estimate then I'll be able to plan around it -- whether it's likely to be fixed next week or next year or somewhere in between.
The text was updated successfully, but these errors were encountered: