With such a way, I have now that compiler errors "Normal variables can not be accessed with ‘super’, use ‘this’ instead."
Using this, does not allow me to override flash getter/setter, it brings me “infinite loop”…
Any hint to retrieve the desired behavior ?
Thanks.
Stéphane.
Okay, then it’s not related to code completion. “display” is defined when Haxe is performing code completion, or in our case, when we generate our documentation. The Haxe core code uses “doc_gen” as a define only for when generating documentation. There are cases where we blur the lines a little for documentation, since things need to match up exactly (like in this case, is it a property, or a getter/setter?)
Is this really related to Lime and OpenFL being updated? Did you update your Haxe install? I thought it was not possible to call super.x like this, I seem to recall trying to do something similar (and hitting a similar infinite loop on Flash) and having to give up
I have fought a whole mess for that, I admit, but it finally worked that way.
The haxelib upgrade seems to have updated that day…
• openfl 3.4.0 > 3.5.0
• lime 2.7.0 > 2.8.0
• swf 2.1.3 > 2.1.4
Even stranger ! Downgrading back to the previous versions brings me now the compiler error :
C:/HaxeToolkit/haxe/lib/openfl/3,4,0/openfl/display/GradientType.hx:26 characters 0-22 : Recursive typedef is not allowed.
I will try to locate the windows/html5 new issues with openfl 3.5.0/lime 2.8.0 tomorrow.
Anyway, It will be hard. Windows crash after an invalid cast popup, and I did forget how to trace() in HTML.
If you roll back to OpenFL 3.4 and Lime 2.7, be sure to do a -clean Flash build:
openfl test flash -clean
That will fix “recursive typedef” errors after downgrading. For HTML5, trace should work, but you need to open a debugger/inspector (usually Ctrl+Shift+I on Windows browsers) then hit the “console” tab
I believe the “use ‘this’ instead” error is Haxe related, not OpenFL related, but compare and lets see what happens
A lot of compiled swf and various assets, dynamically imported…
A loss of time to update all previous compiled swf and to export back my externs assets I guess/hope.
Will keep you informed of the windows/html5 new issues tomorrow.
Thank for your time.
If you can, maybe you can use an assets directory with ‘embed=“false”’ so it copies to the Export directory, without putting it in your SWF. That may help with allowing clean builds and would help if you test other targets as well. I’m so sorry for the setback
I have one idea for solving the override issue, I’ll need to try it when I’m back to my desk
but no INIT, PROGRESS, or COMPLETE…
Can’t be sure that the HTTPStatus one is a new one…
Any advice ? A random no-cache trick with the URLRequest ?
Thanks.