starry-abyss
commented
7 years ago After upgrading something in haxelib (I guess), I now get the same behaviour on neko in HaxeDevelop 5.2.0.3. I use Win7 64bit. Just doing lime test neko gives the stack trace as expected, but from HaxeDevelop it looks like:
Build succeeded
Done(0)
haxelib run lime run "project.xml" neko -debug
Running process: D:\build\HaxeToolkit\haxe\haxelib.exe run lime run "project.xml" neko -debug
AL lib: (EE) alc_cleanup: 1 device not closed
Done(1)My haxelib list is:
actuate: 1.8.6 [1.8.7]
box2d: [1.2.3]
flixel-addons: [git] separate-render
flixel-demos: [git]
flixel-templates: [1.0.2] git
flixel-tools: 1.1.1 1.1.2 1.1.3 [1.2.1]
flixel-ui: 1.0.2 [2.0.0] git
flixel: [git] separate-render
format: [3.2.1] git
haxelib_client: [3.2.0-rc.3]
hscript: 2.0.5 [2.0.7]
hxcpp: 3.1.48 3.2.102 3.2.193 3.2.205 3.3.49 [3.4.2]
hxtelemetry: 0.3.3 0.3.4 [0.3.5]
layout: [1.2.1]
lime-samples: 2.6.0 [3.4.0]
lime-tools: [1.5.7]
lime: 2.9.0_ 2.9.1 2.9.1_ 3.2.1_ 3.5.2 [git] lars_ openfl3_
nape: [2.0.20]
openfl-samples: 3.3.0 3.3.1 4.0.0 [4.5.1]
openfl: 3.6.0 [3.6.1] 4.2.0 backup3.6.1 git lars openfl3
poly2trihx: [0.1.4]
polygonal-ds: [1.4.1]
polygonal-printf: [1.0.2-beta]
promhx: [1.1.0]
swf: 2.0.3 2.1.3 2.2.0 2.2.4 2.3.0 [2.3.1]
unifill: [0.4.1]
Not on a windows machine myself but: FlashDevelop (and HaxeDevelop for that matter) has a problem showing run-time errors. Running erroneous code from the command line works OK (in that is actually displays the proper error message and the stack trace leading tot the offending line of code) but Haxe-/FlashDevelop only shows the "1 device not closed" error. You can test this pretty easy by, in an OpenFL project, referring to the stage in a class' constructor ('cept for Main::new) or declaring an Int without specifying an initial value and then add 1 to it while targeting Neko.