No, you will have to use Haxe (https://haxe.org/).
@ttt It's not, Neko is a virtual machine and it runs much slower than native HXCPP builds. It's most commonly used during development because it's quick to compile / test with, but for releases, people normally use HXCPP builds for the better performance.
Also note that you can just run
lime test neko instead of
lime test windows -neko.
Check out FlxBasePreloader, which can be extended to be customized. However, we currently skip the preloader on non-web targets:
but I didn't succeed.
That's .. quite vague. :D What exactly was the problem / what have you tried? Did you get an error during compilation? What library versions do you have?
The OpenFL asset system /
openfl.Assets indeed only works for assets included at compile time. This is to allow for consistent code across targets that do have file system access and those that don't. Also, there's an option to embed assets.
What you're looking for are the following methods:
Looks like your connection to HaxeFlixel was lost, please wait while we try to reconnect.