Blog

That was my main concern with NME: regression.

The project is huge and it is easy to break something. Often, after an update, something which worked perfectly would fail. NME was renamed openFL, regressions still happens.

Today I cannot work with iOS, my program launch a white screen on my iPad and I don't have the time to investigate yet.

Someone also told me some days ago that my extension example was not working anymore with the latest openFL.

My advice is, when you have a setup which works, keep it somewhere:

$ haxelib list > haxelib.backup

The next time you have a problem after an haxelib update you will be able to go back to a working state looking at this file and reseting openfl versions to what they where.

As far as I am concerned, I am back to june/july (it may not work for you, sorry):

$ haxelib set openfl 1.0.1
$ haxelib set openfl-compatibility 1.0.1
$ haxelib set openfl-native 1.0.1
$ haxelib set openfl-tools 1.0.2

I am thinking about creating a little script to let me switch to stable / update / git. It would allow me to test updates without worrying too much.