-
Notifications
You must be signed in to change notification settings - Fork 11
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
StaxeXL 0.12.x incompatibility #17
Comments
Thanks Philippe, that would be awesome! There is one important breaking change that may be important for the Toolkit. The default render engine is WebGL now, but Shapes/Graphics are still not supported with this renderer (it will be supported with the next version of StageXL). For the time being, you can switch back the default renderer like this:
|
@bp74 Ha! I was about to report that graphics were not rendering in webGL :) That said, something's strange with Graphics and Canvas2D - but maybe I'm just rusty with StageXL. I didn't expect to have to call beginPath/closePath when drawing multiple colors (without it, the last fill color applies to all the paths).
|
Yes that's right. It's not an invention of StageXL but the behavior of the Canvas drawing API. StageXL uses just a very thin wrapper over this API. |
Do you have an idea when webGL graphics will work? |
I think i will take a few weeks. Currently i'm working on the basics and i can fill solid colors :) Next up are strokes/lines, the non-zero winding rule and after that gradients .. so still some things to do. |
Nice, webGL even in IE11 :) |
StageXL 0.12 introduces API breaking changes.
The toolkit (including v0.6) is compatible with StageXL 0.11.0.
You can update your
pubspec.yaml
file to use this specific version like this:I'm looking to adapt the toolkit to 0.12.
The text was updated successfully, but these errors were encountered: