|
hi zeroid's ;) 2 short observations/bugs(?): -sometimes sos/luminicbox shows this : 'LogLevel::getLevelByKey 73>> key not found [ANY CHARACTER]' i found out that it happens if any of the classes of the project monitored by zeroi has a standard trace-statement... pretty annoying, cause the LogLevel- class broadcasts this message on ERROR-level. -in my classes i categorized my default trace-methods as trace("d [SOME TEXT HERE]"); the more important trace messages have been assigned to INFO-level and real errors are categorized in ERROR and FATAL... however the 'normal' debug-messages don't show up in the debugger; may- be i'm doing something wrong but i'm only able to see them if i change from "d" to "i" i don't use logconfig-features (yet)... but i can't see how this could help with the problems i ran into... any hints from the 'experts'? ;) thx in advance! henrik -------- Original Message --------
dooooh! that's it!!! now sos is responding... :-) for anyone using as2ant; this is how it has to be set up: <mtasc src="" classpath="${src.dir}:${core.dir}:${classCollection.dir}" swf="${build.dir}/${targetswf}" main="false" version="${version}" frame="${classFrame}" trace="org.osflash.zeroi.logging.LoggerClass.log"> <argument value="org/osflash/zeroi/logging/LoggerClass"/> <!-- Outcomment your logging target --> <argument value="org/osflash/zeroi/logging/publisher/SOSPublisher"/> <!-- <argument value="org/osflash/zeroi/logging/publisher/TextFieldPublisher"/> --> <!-- <argument value="org/osflash/zeroi/logging/publisher/XRayPublisher"/> --> <!-- <argument value="org/osflash/zeroi/logging/publisher/LuminicPublisher"/> --> </mtasc> now i'll try to use the logconfig-feature wich sounds really promising when you have a bunch of traces from different classes ;-) thanks for the quick response and 'rock on'! henrik Sönke Rohde wrote:
|
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
