Re: [AD] sys_directx_trace_handler |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Elias Pschernig:
> It says:
> "If the application has no debugger, the system debugger displays the
> string. If the application has no debugger and the system debugger is not
> active, OutputDebugString does nothing."
If I run a program under GDB (MinGW, Windows CLI), I get output of
OutputDebugString(), so I guess sys_directx_trace_handler() makes sense
then? We've also got the _TRACE() macro for that, so I'm a bit confused
here.
> The docs for al_trace:
> "Outputs a debugging trace message, using a printf() format string given
> in ASCII. If you have installed a custom trace handler it uses that, or if
> the environment variable ALLEGRO_TRACE is set it writes into the file
> specified by the environment, otherwise it writes the message to
> "allegro.log" in the current directory. You will usually want to use the
> TRACE() macro instead of calling this function directly."
Note that _TRACE() and TRACE() behave differently.
--
Daniel Schlyder
http://bitblaze.com/