]> git.saurik.com Git - wxWidgets.git/blame_incremental - docs/latex/wx/log.tex
fixed indentation in case there's only one cell on line
[wxWidgets.git] / docs / latex / wx / log.tex
... / ...
CommitLineData
1%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
2%% Name: log.tex
3%% Purpose: wxLog and related classes documentation
4%% Author: Vadim Zeitlin
5%% Modified by:
6%% Created: some time ago
7%% RCS-ID: $Id$
8%% Copyright: (c) 1997-2001 Vadim Zeitlin
9%% License: wxWidgets license
10%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
11
12\section{\class{wxLog}}\label{wxlog}
13
14wxLog class defines the interface for the {\it log targets} used by wxWidgets
15logging functions as explained in the \helpref{wxLog overview}{wxlogoverview}.
16The only situations when you need to directly use this class is when you want
17to derive your own log target because the existing ones don't satisfy your
18needs. Another case is if you wish to customize the behaviour of the standard
19logging classes (all of which respect the wxLog settings): for example, set
20which trace messages are logged and which are not or change (or even remove
21completely) the timestamp on the messages.
22
23Otherwise, it is completely hidden behind the {\it wxLogXXX()} functions and
24you may not even know about its existence.
25
26See \helpref{log overview}{wxlogoverview} for the descriptions of wxWidgets
27logging facilities.
28
29\wxheading{Derived from}
30
31No base class
32
33\wxheading{Include files}
34
35<wx/log.h>
36
37\latexignore{\rtfignore{\wxheading{Function groups}}}
38
39\membersection{Static functions}
40
41The functions in this section work with and manipulate the active log target.
42The \helpref{OnLog()}{wxlogonlog} is called by the {\it wxLogXXX()} functions
43and invokes the \helpref{DoLog()}{wxlogdolog} of the active log target if any.
44Get/Set methods are used to install/query the current active target and,
45finally, \helpref{DontCreateOnDemand()}{wxlogdontcreateondemand} disables the
46automatic creation of a standard log target if none actually exists. It is
47only useful when the application is terminating and shouldn't be used in other
48situations because it may easily lead to a loss of messages.
49
50\helpref{OnLog}{wxlogonlog}\\
51\helpref{GetActiveTarget}{wxloggetactivetarget}\\
52\helpref{SetActiveTarget}{wxlogsetactivetarget}\\
53\helpref{DontCreateOnDemand}{wxlogdontcreateondemand}\\
54\helpref{Suspend}{wxlogsuspend}\\
55\helpref{Resume}{wxlogresume}
56
57\membersection{Logging functions}
58
59There are two functions which must be implemented by any derived class to
60actually process the log messages: \helpref{DoLog}{wxlogdolog} and
61\helpref{DoLogString}{wxlogdologstring}. The second function receives a string
62which just has to be output in some way and the easiest way to write a new log
63target is to override just this function in the derived class. If more control
64over the output format is needed, then the first function must be overridden
65which allows to construct custom messages depending on the log level or even
66do completely different things depending on the message severity (for example,
67throw away all messages except warnings and errors, show warnings on the
68screen and forward the error messages to the user's (or programmer's) cell
69phone - maybe depending on whether the timestamp tells us if it is day or
70night in the current time zone).
71
72There also functions to support message buffering. Why are they needed?
73Some of wxLog implementations, most notably the standard wxLogGui class,
74buffer the messages (for example, to avoid showing the user a zillion of modal
75message boxes one after another -- which would be really annoying).
76\helpref{Flush()}{wxlogflush} shows them all and clears the buffer contents.
77This function doesn't do anything if the buffer is already empty.
78
79\helpref{Flush}{wxlogflush}\\
80\helpref{FlushActive}{wxlogflushactive}
81
82\membersection{Customization}\label{wxlogcustomization}
83
84The functions below allow some limited customization of wxLog behaviour
85without writing a new log target class (which, aside of being a matter of
86several minutes, allows you to do anything you want).
87
88The verbose messages are the trace messages which are not disabled in the
89release mode and are generated by \helpref{wxLogVerbose}{wxlogverbose}. They
90are not normally shown to the user because they present little interest, but
91may be activated, for example, in order to help the user find some program
92problem.
93
94As for the (real) trace messages, their handling depends on the settings of
95the (application global) {\it trace mask}. There are two ways to specify it:
96either by using \helpref{SetTraceMask}{wxlogsettracemask} and
97\helpref{GetTraceMask}{wxloggettracemask} and using
98\helpref{wxLogTrace}{wxlogtrace} which takes an integer mask or by using
99\helpref{AddTraceMask}{wxlogaddtracemask} for string trace masks.
100
101The difference between bit-wise and string trace masks is that a message using
102integer trace mask will only be logged if all bits of the mask are set in the
103current mask while a message using string mask will be logged simply if the
104mask had been added before to the list of allowed ones.
105
106For example,
107
108\begin{verbatim}
109// wxTraceOleCalls is one of standard bit masks
110wxLogTrace(wxTraceRefCount | wxTraceOleCalls, "Active object ref count: %d", nRef);
111\end{verbatim}
112will do something only if the current trace mask contains both
113{\tt wxTraceRefCount} and {\tt wxTraceOle}, but
114
115\begin{verbatim}
116// wxTRACE_OleCalls is one of standard string masks
117wxLogTrace(wxTRACE_OleCalls, "IFoo::Bar() called");
118\end{verbatim}
119
120will log the message if it was preceded by
121
122\begin{verbatim}
123wxLog::AddTraceMask(wxTRACE_OleCalls);
124\end{verbatim}
125
126Using string masks is simpler and allows to easily add custom ones, so this is
127the preferred way of working with trace messages. The integer trace mask is
128kept for compatibility and for additional (but very rarely needed) flexibility
129only.
130
131The standard trace masks are given in \helpref{wxLogTrace}{wxlogtrace}
132documentation.
133
134Finally, the {\it wxLog::DoLog()} function automatically prepends a time stamp
135to all the messages. The format of the time stamp may be changed: it can be
136any string with \% specifications fully described in the documentation of the
137standard {\it strftime()} function. For example, the default format is
138"[\%d/\%b/\%y \%H:\%M:\%S] " which gives something like "[17/Sep/98 22:10:16] "
139(without quotes) for the current date. Setting an empty string as the time
140format disables timestamping of the messages completely.
141
142{\bf NB:} Timestamping is disabled for Visual C++ users in debug builds by
143default because otherwise it would be impossible to directly go to the line
144from which the log message was generated by simply clicking in the debugger
145window on the corresponding error message. If you wish to enable it, please use
146\helpref{SetTimestamp}{wxlogsettimestamp} explicitly.
147
148\helpref{AddTraceMask}{wxlogaddtracemask}\\
149\helpref{RemoveTraceMask}{wxlogremovetracemask}\\
150\helpref{ClearTraceMasks}{wxlogcleartracemasks}\\
151\helpref{GetTraceMasks}{wxloggettracemasks}\\
152\helpref{IsAllowedTraceMask}{wxlogisallowedtracemask}\\
153\helpref{SetVerbose}{wxlogsetverbose}\\
154\helpref{GetVerbose}{wxloggetverbose}\\
155\helpref{SetTimestamp}{wxlogsettimestamp}\\
156\helpref{GetTimestamp}{wxloggettimestamp}\\
157\helpref{SetTraceMask}{wxlogsettracemask}\\
158\helpref{GetTraceMask}{wxloggettracemask}
159
160%%%%% MEMBERS HERE %%%%%
161\helponly{\insertatlevel{2}{
162
163\wxheading{Members}
164
165}}
166
167\membersection{wxLog::AddTraceMask}\label{wxlogaddtracemask}
168
169\func{static void}{AddTraceMask}{\param{const wxString\& }{mask}}
170
171Add the {\it mask} to the list of allowed masks for
172\helpref{wxLogTrace}{wxlogtrace}.
173
174\wxheading{See also}
175
176\helpref{RemoveTraceMask}{wxlogremovetracemask}
177\helpref{GetTraceMasks}{wxloggettracemasks}
178
179\membersection{wxLog::ClearTraceMasks}\label{wxlogcleartracemasks}
180
181\func{static void}{ClearTraceMasks}{\void}
182
183Removes all trace masks previously set with
184\helpref{AddTraceMask}{wxlogaddtracemask}.
185
186\wxheading{See also}
187
188\helpref{RemoveTraceMask}{wxlogremovetracemask}
189
190\membersection{wxLog::GetTraceMasks}\label{wxloggettracemasks}
191
192\func{static const wxArrayString \&}{GetTraceMasks}{\void}
193
194Returns the currently allowed list of string trace masks.
195
196\wxheading{See also}
197
198\helpref{AddTraceMask}{wxlogaddtracemask}.
199
200\membersection{wxLog::OnLog}\label{wxlogonlog}
201
202\func{static void}{OnLog}{\param{wxLogLevel }{ level}, \param{const char * }{ message}}
203
204Forwards the message at specified level to the {\it DoLog()} function of the
205active log target if there is any, does nothing otherwise.
206
207\membersection{wxLog::GetActiveTarget}\label{wxloggetactivetarget}
208
209\func{static wxLog *}{GetActiveTarget}{\void}
210
211Returns the pointer to the active log target (may be NULL).
212
213\membersection{wxLog::SetActiveTarget}\label{wxlogsetactivetarget}
214
215\func{static wxLog *}{SetActiveTarget}{\param{wxLog * }{ logtarget}}
216
217Sets the specified log target as the active one. Returns the pointer to the
218previous active log target (may be NULL).
219
220\membersection{wxLog::Suspend}\label{wxlogsuspend}
221
222\func{static void}{Suspend}{\void}
223
224Suspends the logging until \helpref{Resume}{wxlogresume} is called. Note that
225the latter must be called the same number of times as the former to undo it,
226i.e. if you call Suspend() twice you must call Resume() twice as well.
227
228Note that suspending the logging means that the log sink won't be be flushed
229periodically, it doesn't have any effect if the current log target does the
230logging immediately without waiting for \helpref{Flush}{wxlogflush} to be
231called (the standard GUI log target only shows the log dialog when it is
232flushed, so Suspend() works as expected with it).
233
234\wxheading{See also}
235
236\helpref{Resume}{wxlogresume},\\
237\helpref{wxLogNull}{wxlogoverview}
238
239\membersection{wxLog::Resume}\label{wxlogresume}
240
241\func{static void}{Resume}{\void}
242
243Resumes logging previously suspended by a call to
244\helpref{Suspend}{wxlogsuspend}. All messages logged in the meanwhile will be
245flushed soon.
246
247\membersection{wxLog::DoLog}\label{wxlogdolog}
248
249\func{virtual void}{DoLog}{\param{wxLogLevel }{level}, \param{const wxChar }{*msg}, \param{time\_t }{timestamp}}
250
251Called to process the message of the specified severity. {\it msg} is the text
252of the message as specified in the call of {\it wxLogXXX()} function which
253generated it and {\it timestamp} is the moment when the message was generated.
254
255The base class version prepends the timestamp to the message, adds a prefix
256corresponding to the log level and then calls
257\helpref{DoLogString}{wxlogdologstring} with the resulting string.
258
259\membersection{wxLog::DoLogString}\label{wxlogdologstring}
260
261\func{virtual void}{DoLogString}{\param{const wxChar }{*msg}, \param{time\_t }{timestamp}}
262
263Called to log the specified string. The timestamp is already included into the
264string but still passed to this function.
265
266A simple implementation may just send the string to {\tt stdout} or, better,
267{\tt stderr}.
268
269\membersection{wxLog::DontCreateOnDemand}\label{wxlogdontcreateondemand}
270
271\func{static void}{DontCreateOnDemand}{\void}
272
273Instructs wxLog to not create new log targets on the fly if there is none
274currently. (Almost) for internal use only: it is supposed to be called by the
275application shutdown code.
276
277Note that this function also calls
278\helpref{ClearTraceMasks}{wxlogcleartracemasks}.
279
280\membersection{wxLog::Flush}\label{wxlogflush}
281
282\func{virtual void}{Flush}{\void}
283
284Shows all the messages currently in buffer and clears it. If the buffer
285is already empty, nothing happens.
286
287\membersection{wxLog::FlushActive}\label{wxlogflushactive}
288
289\func{static void}{FlushActive}{\void}
290
291Flushes the current log target if any, does nothing if there is none.
292
293\wxheading{See also}
294
295\helpref{Flush}{wxlogflush}
296
297\membersection{wxLog::SetVerbose}\label{wxlogsetverbose}
298
299\func{static void}{SetVerbose}{\param{bool }{ verbose = true}}
300
301Activates or deactivates verbose mode in which the verbose messages are
302logged as the normal ones instead of being silently dropped.
303
304\membersection{wxLog::GetVerbose}\label{wxloggetverbose}
305
306\func{static bool}{GetVerbose}{\void}
307
308Returns whether the verbose mode is currently active.
309
310\membersection{wxLog::SetLogLevel}\label{wxlogsetloglevel}
311
312\func{static void}{SetLogLevel}{\param{wxLogLevel }{ logLevel}}
313
314Specifies that log messages with $level > logLevel$ should be ignored
315and not sent to the active log target.
316
317\membersection{wxLog::GetLogLevel}\label{wxloggetloglevel}
318
319\func{static wxLogLevel}{GetLogLevel}{\void}
320
321Returns the current log level limit.
322
323\membersection{wxLog::SetTimestamp}\label{wxlogsettimestamp}
324
325\func{void}{SetTimestamp}{\param{const char * }{ format}}
326
327Sets the timestamp format prepended by the default log targets to all
328messages. The string may contain any normal characters as well as \%
329prefixed format specificators, see {\it strftime()} manual for details.
330Passing a NULL value (not empty string) to this function disables message timestamping.
331
332\membersection{wxLog::GetTimestamp}\label{wxloggettimestamp}
333
334\constfunc{const char *}{GetTimestamp}{\void}
335
336Returns the current timestamp format string.
337
338\membersection{wxLog::SetTraceMask}\label{wxlogsettracemask}
339
340\func{static void}{SetTraceMask}{\param{wxTraceMask }{ mask}}
341
342Sets the trace mask, see \helpref{Customization}{wxlogcustomization}
343section for details.
344
345\membersection{wxLog::GetTraceMask}\label{wxloggettracemask}
346
347Returns the current trace mask, see \helpref{Customization}{wxlogcustomization} section
348for details.
349
350\membersection{wxLog::IsAllowedTraceMask}\label{wxlogisallowedtracemask}
351
352\func{static bool}{IsAllowedTraceMask}{\param{const wxChar *}{mask}}
353
354Returns true if the {\it mask} is one of allowed masks for
355\helpref{wxLogTrace}{wxlogtrace}.
356
357See also: \helpref{AddTraceMask}{wxlogaddtracemask},
358\helpref{RemoveTraceMask}{wxlogremovetracemask}
359
360\membersection{wxLog::RemoveTraceMask}\label{wxlogremovetracemask}
361
362\func{static void}{RemoveTraceMask}{\param{const wxString\& }{mask}}
363
364Remove the {\it mask} from the list of allowed masks for
365\helpref{wxLogTrace}{wxlogtrace}.
366
367See also: \helpref{AddTraceMask}{wxlogaddtracemask}
368
369%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogChain %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
370
371\section{\class{wxLogChain}}\label{wxlogchain}
372
373This simple class allows to chain log sinks, that is to install a new sink but
374keep passing log messages to the old one instead of replacing it completely as
375\helpref{SetActiveTarget}{wxlogsetactivetarget} does.
376
377It is especially useful when you want to divert the logs somewhere (for
378example to a file or a log window) but also keep showing the error messages
379using the standard dialogs as \helpref{wxLogGui}{wxlogoverview} does by default.
380
381Example of usage:
382
383\begin{verbatim}
384wxLogChain *logChain = new wxLogChain(new wxLogStderr);
385
386// all the log messages are sent to stderr and also processed as usually
387...
388
389// don't delete logChain directly as this would leave a dangling
390// pointer as active log target, use SetActiveTarget() instead
391delete wxLog::SetActiveTarget(...something else or NULL...);
392
393\end{verbatim}
394
395\wxheading{Derived from}
396
397\helpref{wxLog}{wxlog}
398
399\wxheading{Include files}
400
401<wx/log.h>
402
403\latexignore{\rtfignore{\wxheading{Members}}}
404
405\membersection{wxLogChain::wxLogChain}\label{wxlogchainwxlogchain}
406
407\func{}{wxLogChain}{\param{wxLog *}{logger}}
408
409Sets the specified {\tt logger} (which may be {\tt NULL}) as the default log
410target but the log messages are also passed to the previous log target if any.
411
412\membersection{wxLogChain::\destruct{wxLogChain}}
413
414\func{}{\destruct{wxLogChain}}{\void}
415
416Destroys the previous log target.
417
418\membersection{wxLogChain::GetOldLog}\label{wxlogchaingetoldlog}
419
420\constfunc{wxLog *}{GetOldLog}{\void}
421
422Returns the pointer to the previously active log target (which may be {\tt
423NULL}).
424
425\membersection{wxLogChain::IsPassingMessages}\label{wxlogchainispassingmessages}
426
427\constfunc{bool}{IsPassingMessages}{\void}
428
429Returns {\tt true} if the messages are passed to the previously active log
430target (default) or {\tt false} if \helpref{PassMessages}{wxlogchainpassmessages}
431had been called.
432
433\membersection{wxLogChain::PassMessages}\label{wxlogchainpassmessages}
434
435\func{void}{PassMessages}{\param{bool }{passMessages}}
436
437By default, the log messages are passed to the previously active log target.
438Calling this function with {\tt false} parameter disables this behaviour
439(presumably temporarily, as you shouldn't use wxLogChain at all otherwise) and
440it can be reenabled by calling it again with {\it passMessages} set to {\tt
441true}.
442
443\membersection{wxLogChain::SetLog}\label{wxlogchainsetlog}
444
445\func{void}{SetLog}{\param{wxLog *}{logger}}
446
447Sets another log target to use (may be {\tt NULL}). The log target specified
448in the \helpref{constructor}{wxlogchainwxlogchain} or in a previous call to
449this function is deleted.
450
451This doesn't change the old log target value (the one the messages are
452forwarded to) which still remains the same as was active when wxLogChain
453object was created.
454
455%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogGui %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
456
457\section{\class{wxLogGui}}\label{wxloggui}
458
459This is the default log target for the GUI wxWidgets applications. It is passed
460to \helpref{wxLog::SetActiveTarget}{wxlogsetactivetarget} at the program
461startup and is deleted by wxWidgets during the program shut down.
462
463\wxheading{Derived from}
464
465\helpref{wxLog}{wxlog}
466
467\wxheading{Include files}
468
469<wx/log.h>
470
471\latexignore{\rtfignore{\wxheading{Members}}}
472
473\membersection{wxLogGui::wxLogGui}
474
475\func{}{wxLogGui}{\void}
476
477Default constructor.
478
479%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogNull %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
480
481\section{\class{wxLogNull}}\label{wxlognull}
482
483This class allows to temporarily suspend logging. All calls to the log
484functions during the life time of an object of this class are just ignored.
485
486In particular, it can be used to suppress the log messages given by wxWidgets
487itself but it should be noted that it is rarely the best way to cope with this
488problem as {\bf all} log messages are suppressed, even if they indicate a
489completely different error than the one the programmer wanted to suppress.
490
491For instance, the example of the overview:
492
493{\small
494\begin{verbatim}
495 wxFile file;
496
497 // wxFile.Open() normally complains if file can't be opened, we don't want it
498 {
499 wxLogNull logNo;
500 if ( !file.Open("bar") )
501 ... process error ourselves ...
502 } // ~wxLogNull called, old log sink restored
503
504 wxLogMessage("..."); // ok
505\end{verbatim}
506}%
507
508would be better written as:
509
510{\small
511\begin{verbatim}
512 wxFile file;
513
514 // don't try to open file if it doesn't exist, we are prepared to deal with
515 // this ourselves - but all other errors are not expected
516 if ( wxFile::Exists("bar") )
517 {
518 // gives an error message if the file couldn't be opened
519 file.Open("bar");
520 }
521 else
522 {
523 ...
524 }
525\end{verbatim}
526}%
527
528\wxheading{Derived from}
529
530\helpref{wxLog}{wxlog}
531
532\wxheading{Include files}
533
534<wx/log.h>
535
536\latexignore{\rtfignore{\wxheading{Members}}}
537
538\membersection{wxLogNull::wxLogNull}
539
540\func{}{wxLogNull}{\void}
541
542Suspends logging.
543
544\membersection{wxLogNull::\destruct{wxLogNull}}
545
546Resumes logging.
547
548%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogPassThrough %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
549
550\section{\class{wxLogPassThrough}}\label{wxlogpassthrough}
551
552A special version of \helpref{wxLogChain}{wxlogchain} which uses itself as the
553new log target. Maybe more clearly, it means that this is a log target which
554forwards the log messages to the previously installed one in addition to
555processing them itself.
556
557Unlike \helpref{wxLogChain}{wxlogchain} which is usually used directly as is,
558this class must be derived from to implement \helpref{DoLog}{wxlogdolog}
559and/or \helpref{DoLogString}{wxlogdologstring} methods.
560
561\wxheading{Derived from}
562
563\helpref{wxLogChain}{wxlogchain}
564
565\wxheading{Include files}
566
567<wx/log.h>
568
569\latexignore{\rtfignore{\wxheading{Members}}}
570
571\membersection{wxLogPassThrough::wxLogPassThrough}\label{wxlogpassthroughctor}
572
573Default ctor installs this object as the current active log target.
574
575%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogStderr %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
576
577\section{\class{wxLogStderr}}\label{wxlogstderr}
578
579This class can be used to redirect the log messages to a C file stream (not to
580be confused with C++ streams). It is the default log target for the non-GUI
581wxWidgets applications which send all the output to {\tt stderr}.
582
583\wxheading{Derived from}
584
585\helpref{wxLog}{wxlog}
586
587\wxheading{Include files}
588
589<wx/log.h>
590
591\wxheading{See also}
592
593\helpref{wxLogStream}{wxlogstream}
594
595\latexignore{\rtfignore{\wxheading{Members}}}
596
597\membersection{wxLogStderr::wxLogStderr}
598
599\func{}{wxLogStderr}{\param{FILE }{*fp = NULL}}
600
601Constructs a log target which sends all the log messages to the given
602{\tt FILE}. If it is {\tt NULL}, the messages are sent to {\tt stderr}.
603
604%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogStream %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
605
606\section{\class{wxLogStream}}\label{wxlogstream}
607
608This class can be used to redirect the log messages to a C++ stream.
609
610Please note that this class is only available if wxWidgets was compiled with
611the standard iostream library support ({\tt wxUSE\_STD\_IOSTREAM} must be on).
612
613\wxheading{Derived from}
614
615\helpref{wxLog}{wxlog}
616
617\wxheading{Include files}
618
619<wx/log.h>
620
621\wxheading{See also}
622
623\helpref{wxLogStderr}{wxlogstderr},\\
624\helpref{wxStreamToTextRedirector}{wxstreamtotextredirector}
625
626\latexignore{\rtfignore{\wxheading{Members}}}
627
628\membersection{wxLogStream::wxLogStream}
629
630\func{}{wxLogStream}{\param{std::ostream }{*ostr = NULL}}
631
632Constructs a log target which sends all the log messages to the given
633output stream. If it is {\tt NULL}, the messages are sent to {\tt cerr}.
634
635%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogTextCtrl %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
636
637\section{\class{wxLogTextCtrl}}\label{wxlogtextctrl}
638
639Using these target all the log messages can be redirected to a text control.
640The text control must have been created with {\tt wxTE\_MULTILINE} style by the
641caller previously.
642
643\wxheading{Derived from}
644
645\helpref{wxLog}{wxlog}
646
647\wxheading{Include files}
648
649<wx/log.h>
650
651\wxheading{See also}
652
653\helpref{wxLogTextCtrl}{wxlogtextctrl},\\
654\helpref{wxStreamToTextRedirector}{wxstreamtotextredirector}
655
656\latexignore{\rtfignore{\wxheading{Members}}}
657
658\membersection{wxLogTextCtrl::wxLogTextCtrl}
659
660\func{}{wxLogTextCtrl}{\param{wxTextCtrl }{*textctrl}}
661
662Constructs a log target which sends all the log messages to the given text
663control. The {\it textctrl} parameter cannot be {\tt NULL}.
664
665%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% wxLogWindow %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
666
667\section{\class{wxLogWindow}}\label{wxlogwindow}
668
669This class represents a background log window: to be precise, it collects all
670log messages in the log frame which it manages but also passes them on to the
671log target which was active at the moment of its creation. This allows, for
672example, to show all the log messages in a frame but still continue to process
673them normally by showing the standard log dialog.
674
675\wxheading{Derived from}
676
677\helpref{wxLogPassThrough}{wxlogpassthrough}
678
679\wxheading{Include files}
680
681<wx/log.h>
682
683\wxheading{See also}
684
685\helpref{wxLogTextCtrl}{wxlogtextctrl}
686
687\latexignore{\rtfignore{\wxheading{Members}}}
688
689\membersection{wxLogWindow::wxLogWindow}
690
691\func{}{wxLogWindow}{\param{wxFrame }{*parent}, \param{const wxChar }{*title}, \param{bool }{show = {\tt true}}, \param{bool }{passToOld = {\tt true}}}
692
693Creates the log frame window and starts collecting the messages in it.
694
695\wxheading{Parameters}
696
697\docparam{parent}{The parent window for the log frame, may be {\tt NULL}}
698
699\docparam{title}{The title for the log frame}
700
701\docparam{show}{{\tt true} to show the frame initially (default), otherwise
702\helpref{wxLogWindow::Show}{wxlogwindowshow} must be called later.}
703
704\docparam{passToOld}{{\tt true} to process the log messages normally in addition to
705logging them in the log frame (default), {\tt false} to only log them in the
706log frame.}
707
708\membersection{wxLogWindow::Show}\label{wxlogwindowshow}
709
710\func{void}{Show}{\param{bool }{show = {\tt true}}}
711
712Shows or hides the frame.
713
714\membersection{wxLogWindow::GetFrame}
715
716\constfunc{wxFrame *}{GetFrame}{\void}
717
718Returns the associated log frame window. This may be used to position or resize
719it but use \helpref{wxLogWindow::Show}{wxlogwindowshow} to show or hide it.
720
721\membersection{wxLogWindow::OnFrameCreate}
722
723\func{virtual void}{OnFrameCreate}{\param{wxFrame }{*frame}}
724
725Called immediately after the log frame creation allowing for
726any extra initializations.
727
728\membersection{wxLogWindow::OnFrameClose}\label{wxlogwindowonframeclose}
729
730\func{virtual void}{OnFrameClose}{\param{wxFrame }{*frame}}
731
732Called if the user closes the window interactively, will not be
733called if it is destroyed for another reason (such as when program
734exits).
735
736Return {\tt true} from here to allow the frame to close, {\tt false} to
737prevent this from happening.
738
739\wxheading{See also}
740
741\helpref{wxLogWindow::OnFrameDelete}{wxlogwindowonframedelete}
742
743\membersection{wxLogWindow::OnFrameDelete}\label{wxlogwindowonframedelete}
744
745\func{virtual void}{OnFrameDelete}{\param{wxFrame }{*frame}}
746
747Called right before the log frame is going to be deleted: will
748always be called unlike \helpref{OnFrameClose()}{wxlogwindowonframeclose}.
749