Is anyone except me is using -Ddom
? Because there are several bugs, which makes usage of -Ddom
impossible.
Everything is related to OpenFL 4, latest version from haxelib.
1 - Bug with sprite.graphics
2 - Slowness related to BitmapData
For the last issue I even submit pull request 7 months ago, but neither pull request was accepted nor issue was fixed ![:frowning: :frowning:](//community.openfl.org/images/emoji/twitter/frowning.png?v=5)
Thank you for your help ![:slight_smile: :slight_smile:](//community.openfl.org/images/emoji/twitter/slight_smile.png?v=5)
I helped make the DOM target for a project which has since changed to WebGL. I would like to help make the DOM target more consistent, but I know that it has lacked attention ā I wonder sometimes if anyone does use it.
I believe your first bug is fixed, and Lime image gained a version
field so that we can properly track if it changed, so great news, we should now have your optimization in place to speed up canvas-based bitmaps.
I see that some other projects of mine (such as SimpleButton
) seem to have issues, but PiratePig is working. Iām sure we can continue to make DOM better ![:wink: :wink:](//community.openfl.org/images/emoji/twitter/wink.png?v=5)
SimpleButton and mask support have been improved in the latest dev version ![:slight_smile: :slight_smile:](//community.openfl.org/images/emoji/twitter/slight_smile.png?v=5)
Bug with sprite.graphics is fixed in develop.
Slowness related to BitmapData is fixed, but https://github.com/openfl/openfl/commit/54e7235c82f2427a68e592e87adf8c1afbf87e24 breaks alpha animation.
Examples and pull request to fix it - https://github.com/openfl/openfl/pull/1361
Just found another bug in dom renderer ![:sadpanda: :sadpanda:](//community.openfl.org/uploads/default/original/2X/7/7c26de14a214831e52be8dccc6a29f2922eefc2b.png?v=5)
In my big project visibility
partially works, but in this simple example it is not working at all!
Thanks! Everything works now.