hi henrik,
 
thanks for reporting. I just updated zeroi to fix the first one.
The LogLevel isn't checked anymore when no LoggerConfig is used. And the logmessage is changed from ERROR to INFO.
 
I didn't get the second one. Can you please try the new release and check again?
If it still occurs it would be nice if you could send an example.
 
Cheers,
Sönke


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of henrik weber (freemind-design)
Sent: Friday, August 18, 2006 2:15 PM
To: [email protected]
Subject: Re: [osflash] Zeroi is ready to rumble

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 --------
Subject: Re: [osflash] Zeroi is ready to rumble
Date: Thu, 17 Aug 2006 10:41:53 +0200
From: henrik weber (freemind-design) <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
Organization: freemind-design
To: [email protected]
References: <[EMAIL PROTECTED]>


hi sönke!

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:
hi henrik,
 
thanks for your feedback.
the trace-function your are setting is "logtrace" but has to be "log":

org.osflash.zeroi.logging.LoggerClass.log

I hope that is it but anyway I have never tested zeroi with as2ant but should of course work from theory.

 

Cheers,

Sönke

_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org

Reply via email to