I've built a simple application in Flex Builder 3 with some trace() calls. It's an "ActionScript Project", no MXML or AIR involved. I don't run the app from within Eclipse, I just open the generated html file with Firefox.
I'm using the Flash Player 10 Debug version. I've correctly set mm.cnf to log trace output, following the official instructions. A flashlog.txt file is generate in the appropriate location.
Despite all that, trace output is not shown in the log file. What am I doing wrong?
(I suspect it's a compiler option, but I can find no such option in the project options in FlexBuilder)
(If I do run the app from Eclipse, by pressing F11, I can see trace output but only inside Eclipse, not in the log file)
Try setting the -debug compiler argument to true.
Is there anything in the flashlog.txt, or is it completely empty?
Perhaps you can use De MonsterDebugger instead?
De MonsterDebugger is an open source debugger for Adobe Flash, Flex and AIR. De MonsterDebugger is made in Flex and AIR by design studio De Monsters.
If that doesn't work google "fxspy" or "Alcon debugger". Those are two other good debugging options.
Somehow it solved itself
Related
I'm using GPS IDE for Ada 95 coding. When I try to put a break point in a .adb file, I'm getting a message "No source file named filename.adb". I built the project and initialized the debugger. What could have gone wrong?
Oddly, I'm able to execute the program.
Did you enable the debug option for your project? Use Project/"Edit Project Properties" to open the project properties dialog, click the "Switches" tab. Then on each of the Gnatmake, Ada, and Ada Linker tabs check "Debug Information". Close the dialogs, then do a Build/Clean and rebuild your project. (Don't forget to save any changes, do Project/Save All.)
I try to use the example from Adobe help reference as following address:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/mx/controls/Tree.html#includeExamplesSummary
I open FlashDevelop IDE, creat a new Flex 3 project, then copy the code of example to the main.mxml, save it, then run builder.
It failed with "...\TreeExample\TreeExample\src\Main.mxml(5): Error: Could not resolve <s:Application> to a component implementation." error message.
There is a "How to use this example" link beside this example, but I didn't find any useful information I want.
How can I run this example in FlashDevelop IDE?
It seems, that you try to compile component from newer Flex sdk with older one (3.x instead of 4.x)
Download newest from Adobe site:
http://opensource.adobe.com/wiki/display/flexsdk/Flex+SDK
And install it to Flash Develop:
http://www.flashdevelop.org/wikidocs/index.php?title=AS3
I just upgraded out Flex project to use SDK version 4.5.1.21328 and the Flash Builder to version 4.5
All of the sudden, I'm getting several red tags on the Flash Builder: "could not resolve s:State/fx:Script/whatever to a component implementation"
However, the project builds fine with Maven, and seems to work well too.
Does anyone have any information on how to remove these "problems"?
Thanks.
Finally managed to find a workaround. Adding
--namespace+=http://ns.adobe.com/mxml/2009,${flexlib}/mxml-2009-manifest.xml --namespace+=http://www.adobe.com/2006/mxml,${flexlib}/mxml-manifest.xml --namespace+=library://ns.adobe.com/flex/spark,${flexlib}/spark-manifest.xml
to the "Additional compiler arguments" in properties -> Flex Compiler seems to remove all the red markers.
Great tip. Error I was getting was:
Could not resolve <mx:RichTextEditor> to a component implementation.
I had to add the above settings and do the following to get mine to compile.
Here's what I did:
project properties->Flex Build->Path-> Library path tab. press Add SWC...
add C:/Program Files/Adobe/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/libs/mx/mx.swc
Then in the Source Path tab press add folder navigate to:
C:/Program Files/Adobe/Adobe Flash Builder 4.5/sdks/4.5.1/frameworks/projects/mx/src
then add in the namespaces as listed in the above article. That fixed it for me.
Clean.
Just as the commenter said, usually just a strange Flash Builder bug. If Project -> Clean... doesn't fix it, comment or revise question.
Your batch builder might be using a different set of library files than the IDE. Look in Project | Properties under Build Path and see what version of the SDK it's using.
I am trying to build a AS3 only project in Flex....I have tried debug mode, but seems like it takes so long to compile....I can't use trace or check variables...Are there anyway to do debug?? Thanks for the help..
Which version of Flash Player have you installed, you need the debugger version. Check your browser , some browsers like Chrome for instance , come with Flash Player bundled in , but this isn't the version you need. You can also check your application properties, particularly the Run/Debug Settings.
Last but not least, you could also watch this Lee Brimelow tutorial, about using MonsterDebugger
http://gotoandlearn.com/play.php?id=109
I'm pretty new to Eclipse and Mojo (.NET guy). I'm having difficulty debugging. I can set breakpoints and switch to the "Debug" Perspective, but no matter what I can do (I am running in debug mode), I can't seem to get the IDE to stop at a breakpoint in the emulator. I'm sure it's a pretty newbie mistake with Eclipse. Anyone have a good step by step I can follow.
Currently, there is no way to set a breakpoint in eclipse for use with the palm emulator.
As Gtompson83 mentioned, all we've got to work with is the gdb-style command line debugger that is included with the SDK.
Yes it's a pain.
I find it easier to attach to the emulator via ssh (scroll down to "Debugging" section) to view logging, and then just using logging in your app to figure out what is going on.
Palm has a debugger as part of the command line tools. You can set break points and check variables.
Debugger Info
I like using the Ares Debugger/Logger. It works even for code not developed using Ares.
After starting the debug mode in Eclipse (changed debug config for the app to have checked the checkboxes for Inspectable and Mojo debugging),
launch the following URL in your browser (I've had the best results with Google Chrome):
http://ares.palm.com/AresDebug/ (you can use also AresLog for logger)
For AresDebug you may need to adjust the Script Filter to start with whatever your appinfo.json file has for the "id" value, then press Get Scripts. Then you're basically good to go. You can select another *.js file and set breakpoints, etc.