Hi everyone,

maybe someone has experience with mx.logging.* usage in F2,
I was trying to implement mx.logging with custom debug application
that uses LocalConnection. I tried to use MiniDebugTarget which uses
LocalConnection as medium,
Maybe I don't understand logging correctly but I though that
MiniDebugTarget should simply logs data into listening connection (so
my custom debug target can trace incoming logs),

But what is not quite clear for me is:
- my custom Log application (standalone) need to be connected to
local connection change with well known name (say "_mdbtrace")
- I thought that MiniDebugTarget simply sends data to "_mdbtrace"
specified in constructor but in constructor it actually tries to
connect to local connection with the same name, so if my custom
loggin application is already started and listening for data,
MiniDebugTarget throws error from constructor because connection
fails,
I've ended with custom subclass of LineFormattedTarget providing
different implementation of MiniDebugTarget and that works quite well,
Now I can start my debug application at any time and my custom
MiniDebugTarget class can send data into connection at any time,

Question:
is that correct what Iv'e done (custom Debug application
window and custom MiniDebugTarget implementation) or maybe I took
wrong way with that?

LiveDocs have example of custom logging implementation:
http://livedocs.macromedia.com/labs/1/flex20beta3/00001881.html

thanks for input,
kind regards,
Peter Blazejewicz

as side-note: I want to thank to Adobe team for releasing source
files - I was be able to find what's wrong after looking into sources,







--
Flexcoders Mailing List
FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt
Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com




SPONSORED LINKS
Web site design development Computer software development Software design and development
Macromedia flex Software development best practice


YAHOO! GROUPS LINKS




Reply via email to