Trazzle
Trazzle is a console tool for debugging flash content. It enables you to visually differentiate several levels of messages, like debug messages, error messages, warnings or fatal errors. Furthermore you can even decide which messages are important for your task you are currently working on and hide everything else.
Trazzle brings two built-in themes and enables you to create your very own ones. Take a look at the complete feature list ...
Features
- Theme support
- Stacktraces (AS3 only)
- Message levels
- Powerful filters
- File monitoring (get notified when a file changes on your filesystem, eg. to reload external content)
- Support for cross-domain policy file
- Log classes for AS2 and AS3
- Auto-update
Requirements
- Mac OS X 10.5
- Internet access for the auto-update feature
- MTASC, MXMLC (Flex) or Flash IDE
Screenshots
Actionscript 3 Usage
- Check the source files out from repository into one of your class folders
- add
-verbose-stacktraces=trueto your MXMLC compiler flags, if you haven't already - Call log() instead of trace()
Actionscript 3/Flex Usage
More information and example code coming soon.
Actionscript 2 Usage
- Check the source files out from repository into one of your class folders
- Set Trazzle class as trace class in mtasc with
-trace com.nesium.Trazzle.trace com/nesium/Trazzle.as - trace calls will automatically be redirected to Trazzle
- Trazzle does not show any trace messages
-
Make sure you have filtering disabled. You can see that filtering is on, if the window title has an asterisk appended.
- Is it possible to use Trazzle from my Virtual Machine?
-
Yes. But you need to change the server address in the log class to your local IP.
- My AS3 log messages always show me that class and method are 'unknown'. What am I doing wrong?
-
Make sure that you have specified the flag
-verbose-stacktraces=truewhen compiling with MXMLC. - I found a bug, what shall I do?
-
Please file bugs and feature requests here.
- Trazzle messes up my stacktrace / Shows wrong method name for my AS3 project
-
I hoped that would not happen. Please click in the application menu, hold the option key and select “Enable debugging output”. This writes every received message from flash to ~/Library/Application Support/Trazzle/Logs/Debug.log. Open this file and find the log message which didn’t show up correctly, copy it and file a bug with the log message as the body here. Please make sure you disable debugging output afterwards, or Trazzle will mercilessly write each and every log message to your disk.