Re: [AD] [patch] register_trace_handler() MacOS/DirectX issue |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: Coordination of admins/developers of the game programming library Allegro <alleg-developers@xxxxxxxxxx>
- Subject: Re: [AD] [patch] register_trace_handler() MacOS/DirectX issue
- From: Daniel Schlyder <daniel@xxxxxxxxxx>
- Date: Wed, 13 Dec 2006 11:34:09 +0100
Peter Wang wrote:
Committed. I'm not sure, but maybe some documentation needs to be
updated? I did not see anywhere that register_trace_handler actually
can be called before initialising Allegro, but it seems the right thing
to allow it.
The attached patch ok?
--
Daniel Schlyder
Index: docs/src/allegro._tx
===================================================================
--- docs/src/allegro._tx (revision 7650)
+++ docs/src/allegro._tx (working copy)
@@ -14800,7 +14800,8 @@
return non-zero if it has processed the error, or zero to continue with
the default actions. You could use this to ignore assert failures, or to
display the error messages on a graphics mode screen without aborting the
- program. Example:
+ program. You can call this function even when Allegro has not been
+ initialised. Example:
<codeblock>
int show_but_continue(const char *text)
{
@@ -14819,7 +14820,8 @@
callback will be passed a formatted error message in ASCII, and should
return non-zero if it has processed the message, or zero to continue with
the default actions. You could use this to ignore trace output, or to
- display the messages on a second monochrome monitor, etc. Example:
+ display the messages on a second monochrome monitor, etc. You can call this
+ function even when Allegro has not been initialised. Example:
<codeblock>
int network_broadcaster(const char *text)
{