I've updated my Flex logging target with the possibility to log directly to a text file. Good thing is that you can switch live between catching the log entries in the panel or writing them to a file. Read this blog post to find out how to write logging messages for XPanelOnAIR using Flex' built-in logging framework.
Please note: I didn't bother making the update run automatically,
so you'd better uninstall any previously installed versions first.
Happy logging !
4 Comments
Thank-you for this very useful tool!!!
I noticed that it hangs (uses all available CPU for quite awhile) when displaying large messages – HTTPService response messages for example if the response is few kilobytes. To get around this:
* I added a “shortMessage” field to the created object in dispatchMessage, which contains just the first 100 characters of the message string.
* I changed the “message” dataField to “shortMessage” in the datagrid
In addition, in LogMessageDetail
* I changed the Text field to a TextArea field (to get scrollbars for long messages)
* changed the width from 400 to 600 (makes some messages easier to read, and there’s plenty of room)
One problem this introduces:
* When you generate the CSV file, it saves the shortMessage, not the message
But i didn’t take time to fix.
Also, I compiled XPanelDebugTarget into a .swc file so that it’s similar to other libraries I use in my project.
Anyway, I thought I would share this in case it helps others.
Thank-you again for a terrific tool!
-dallan
You’re welcome.
Concerning the long messages, please note that you can double-click a log entry in the datagrid. This opens that log message in a popup, with the message in a TextArea.
I’ve noticed that sometimes my logging tool hangs after many log entries, that’s why I added the log-to-file option which makes it possible to generate many Megabytes of log entries.
Feel free to modify & re-distribute it as you wish.
Thanks for your comment.
I noticed that you could double-click on long messages too. That’s why I changed the Text field to a TextArea field in LogMessageDetail.
The big problem though, is that long messages (say > 10K, which can be generated by rpc logging) cause the datagrid to *hang*. XPanelOnAIR becomes completely unresponsive and you have to restart it. That’s why I added a truncated shortMessage field to the object and had the datagrid display that instead of the message.
Just thought others might have this problem as well.
-dallan
Ok thanks, now I fully understand the issue… Good idea, I’ll integrate your fix with the truncated message soon.