Mon 18 Jun 2007 11:43:34 PM UTC, original submission:
In a mailing-list message I haven't sent yet, I'll say:
| (b) Messages written to a wxLog appear asynchronously,
| in idle time, provided that no higher-priority message
| is queued--so an "error" displaces a "warning".
At least I think that's the case.
I was sure I'd read that somewhere, but right now I can't
find it in the wx-2.8.0 help file. It was in wx-2.5.4
help for "wxLog classes overview", under "wxLogMessage":
Notice that the standard behaviour is to not show
informational messages if there are any errors later -
the logic being that the later error messages make the
informational messages preceding them meaningless.
but that's absent in wx-2.8.0 . A deliberate change?
It seemed like an important point to me. And even in the
wx-2.5.4 help file, it isn't obvious to me whether only
wxLogMessage is suppressed if a wxLogError arises before
the wxLogMessage is displayed. Would a wxLogSysError
suppress a wxLogError? Would a wxLogWarning suppress (or
be suppressed by) anything? I don't need to know this
today; I'd just like to see it in the help file (or a
technote, or wherever), because I'll probably want to
know someday.
And I had a hard time finding documentation that logs are
flushed in idle time. It's explained under wxApp::Yield();
a pointer to that in "wxLog classes overview" might help.
One last "wxLog classes overview" thought: would it be
good to provide hyperlinks for wxLogFatalError and the
other functions that are listed in boldface?
|