| Re: [AD] al_register_trace_handler resurrection |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Simple handler is enough, there is no need for al_trace(). I will add
al_register_trace_handler() soon.
On 9 November 2011 02:21, Peter Wang <novalazy@xxxxxxxxxx> wrote:
> On Wed, 9 Nov 2011 01:57:09 +0100, Michał Cichoń <michcic@xxxxxxxxxxxxxx> wrote:
>> Hello,
>>
>> I revived my code which was responsible for redirecting errors logged
>> by Allegro to my console. I was using al_register_trace_handler() to
>> do that, but after an update I notice it was removed:
>>
>> http://svn.tomasu.org/index.cgi/allegro/revision/?rev=13980
>>
>> It was useful because after registering handler before initialization
>> (defined behavior) Allegro.log was not created. All messages was
>> redirected to handler, so I forwarded them into my console. As result
>> one log file was created with engine messages followed by Allegro
>> error messages.
>>
>> Now this functionality is gone and I'm wondering if there is a change
>> of restoring it, because it was handy.
>
> You should be able to add al_register_trace_handler. The tricky part
> about making log messages atomic was if users could call al_trace
> directly, so you probably don't want to add that again.
>
> Peter
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
--
thedmd, Michał Cichoń
Artifex Mundi
michcic@xxxxxxxxxx
http://www.artifexmundi.com