Skip to content
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

Phaser 2.5 breaks EZGUI #57

Closed
TimMensch opened this issue Jun 22, 2016 · 1 comment
Closed

Phaser 2.5 breaks EZGUI #57

TimMensch opened this issue Jun 22, 2016 · 1 comment

Comments

@TimMensch
Copy link

Issues I've seen so far:

  • 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.

@TimMensch
Copy link
Author

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... :)

Sorry again, and good luck with EZGUI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant