-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Published application threads never return results #3
Comments
Try the compiler option -optimize=false |
That works fine after adding this compiler option. I remember it was always configured to false in my maven configuration. But what does the Flex Compiler "really" do when optimize is left to its true default value ? |
It does many things, one the the optimization is to merge all the ABCTags into one, which then make impossible for as3swf to find only the ones needed to create the worker |
OK I will take a look at the compiler code to understand all the fun stuff it does. |
Btw, if you still want to optimize your app, you can still use apparat but with -mergeABC=false |
is mergeABC a hidden compiler option ?!! Is there any hidden options ? |
No I was talking about apparat, a tools which has a swf size reducer feature |
Ah this one https://code.google.com/p/apparat/ I am discovering it |
Hi Frédéric,
When I export an application using easyWorker it seems like threads are never responding. I don't know if they are ran or not, but I am sure that I never get the result. Try publishing https://github.com/riadvice/easyWorker-ActiveAIRCord/ with Flash Builder and run the application.
I used Adobe Scout but it seems like it does not handle workers.
Should I build the application using GradleFX or FlexMojos if it is a Flash Builder issue ? Normally they use the same Flex jar compiler.
Any idea ?
The text was updated successfully, but these errors were encountered: