easyWorker optimize=false

I use your library in a quite big project, and it's very handy ! However it doesn't always works when I deploy it without compiler option "optimize=false" (while it works in debug mode). Unfortunately air package size is much more bigger when optimize=false, is there any way I can remove this option and still get the library work ? On some project, it works fine...

Apr 06 '16 19:04 kisscoool18

I'd love to know what the story with that is too. We may want to use this for an upcoming project and I'm not too happy with having to set that flag.

Apr 07 '16 01:04 Ansury

@kisscoool18 @Ansury Have you found a solution for this? As written here optimize=true does bytecode and filesize optimization. The question is why optimize throws away the ThreadRunner for example.

Oct 13 '16 14:10 D3CK3R

I never did, but I didn't look into it either. Honestly, I hope Flex makes a comeback some day, but we've moved to JavaFX + web start.

Oct 15 '16 06:10 Ansury

In WorkerFactory.as, I re-enabled the commented out code that saves the newly created SWF file to disk. When debug=false and optimize=true, for some reason the doABC tags are stripped from the created SWF. It seems like it's stripping tags from the loaderInfo when set to be optimized.

If anyone can figure out what may be causing this or a workaround I'd be willing to test and help find a solution!

Dec 28 '18 22:12 DigiEggz