Replace TRUE/FALSE with boolean values true/false - part 3

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 35 insertions, 35 deletions

diff --git a/doc/man/man3/tqobject.3qt b/doc/man/man3/tqobject.3qt
index 1db0cf235..e5791aae7 100644
--- a/doc/man/man3/tqobject.3qt
+++ b/doc/man/man3/tqobject.3qt
@@ -74,13 +74,13 @@ Inherits Qt.
 .BI "void \fBkillTimers\fR ()"
 .br
 .ti -1c
-.BI "TQObject * \fBchild\fR ( const char * objName, const char * inheritsClass = 0, bool recursiveSearch = TRUE )"
+.BI "TQObject * \fBchild\fR ( const char * objName, const char * inheritsClass = 0, bool recursiveSearch = true )"
 .br
 .ti -1c
 .BI "const TQObjectList * \fBchildren\fR () const"
 .br
 .ti -1c
-.BI "TQObjectList * \fBqueryList\fR ( const char * inheritsClass = 0, const char * objName = 0, bool regexpMatch = TRUE, bool recursiveSearch = TRUE ) const"
+.BI "TQObjectList * \fBqueryList\fR ( const char * inheritsClass = 0, const char * objName = 0, bool regexpMatch = true, bool recursiveSearch = true ) const"
 .br
 .ti -1c
 .BI "virtual void \fBinsertChild\fR ( TQObject * obj )"
@@ -238,20 +238,20 @@ All signals to and from the object are automatically disconnected.
 .PP
 \fBWarning:\fR Deleting a TQObject while pending events are waiting to be delivered can cause a crash. You must not delete the TQObject directly from a thread that is not the GUI thread. Use the TQObject::deleteLater() method instead, which will cause the event loop to delete the object after all pending events have been delivered to the object.
 .SH "void TQObject::blockSignals ( bool block )"
-Blocks signals if \fIblock\fR is TRUE, or unblocks signals if \fIblock\fR is FALSE.
+Blocks signals if \fIblock\fR is true, or unblocks signals if \fIblock\fR is false.
 .PP
 Emitted signals disappear into hyperspace if signals are blocked. Note that the destroyed() signals will be emitted even if the signals for this object have been blocked.
 .PP
 Examples:
 .)l rot13/rot13.cpp and simple/main.cpp.
 .SH "bool TQObject::checkConnectArgs ( const char * signal, const TQObject * receiver, const char * member )\fC [virtual protected]\fR"
-Returns TRUE if the \fIsignal\fR and the \fImember\fR arguments are compatible; otherwise returns FALSE. (The \fIreceiver\fR argument is currently ignored.)
+Returns true if the \fIsignal\fR and the \fImember\fR arguments are compatible; otherwise returns false. (The \fIreceiver\fR argument is currently ignored.)
 .PP
 \fBWarning:\fR We recommend that you use the default implementation and do not reimplement this function.
-.SH "TQObject * TQObject::child ( const char * objName, const char * inheritsClass = 0, bool recursiveSearch = TRUE )"
+.SH "TQObject * TQObject::child ( const char * objName, const char * inheritsClass = 0, bool recursiveSearch = true )"
 Searches the children and optionally grandchildren of this object, and returns a child that is called \fIobjName\fR that inherits \fIinheritsClass\fR. If \fIinheritsClass\fR is 0 (the default), any class matches.
 .PP
-If \fIrecursiveSearch\fR is TRUE (the default), child() performs a depth-first search of the object's children.
+If \fIrecursiveSearch\fR is true (the default), child() performs a depth-first search of the object's children.
 .PP
 If there is no such object, this function returns 0. If there are more than one, the first one found is retured; if you need all of them, use queryList().
 .SH "void TQObject::childEvent ( TQChildEvent * )\fC [virtual protected]\fR"
@@ -296,7 +296,7 @@ See also name, inherits(), isA(), and isWidgetType().
 .PP
 Example: sql/overview/custom1/main.cpp.
 .SH "bool TQObject::connect ( const TQObject * sender, const char * signal, const TQObject * receiver, const char * member )\fC [static]\fR"
-Connects \fIsignal\fR from the \fIsender\fR object to \fImember\fR in object \fIreceiver\fR, and returns TRUE if the connection succeeds; otherwise returns FALSE.
+Connects \fIsignal\fR from the \fIsender\fR object to \fImember\fR in object \fIreceiver\fR, and returns true if the connection succeeds; otherwise returns false.
 .PP
 You must use the TQ_SIGNAL() and TQ_SLOT() macros when specifying the \fIsignal\fR and the \fImember\fR, for example:
 .PP
@@ -312,7 +312,7 @@ You must use the TQ_SIGNAL() and TQ_SLOT() macros when specifying the \fIsignal\
 .br
 .fi
 .PP
-This example ensures that the label always displays the current scroll bar value. Note that the signal and slots parameters must not contain any variable names, only the type. E.g. the following would not work and return FALSE: TQObject::connect( scroll, TQ_SIGNAL(valueChanged(int v)), label, TQ_SLOT(setNum(int v)) );
+This example ensures that the label always displays the current scroll bar value. Note that the signal and slots parameters must not contain any variable names, only the type. E.g. the following would not work and return false: TQObject::connect( scroll, TQ_SIGNAL(valueChanged(int v)), label, TQ_SLOT(setNum(int v)) );
 .PP
 A signal can also be connected to another signal:
 .PP
@@ -359,7 +359,7 @@ A signal can be connected to many slots and signals. Many signals can be connect
 .PP
 If a signal is connected to several slots, the slots are activated in an arbitrary order when the signal is emitted.
 .PP
-The function returns TRUE if it successfully connects the signal to the slot. It will return FALSE if it cannot create the connection, for example, if TQObject is unable to verify the existence of either \fIsignal\fR or \fImember\fR, or if their signatures aren't compatible.
+The function returns true if it successfully connects the signal to the slot. It will return false if it cannot create the connection, for example, if TQObject is unable to verify the existence of either \fIsignal\fR or \fImember\fR, or if their signatures aren't compatible.
 .PP
 A signal is emitted for \fIevery\fR connection you make, so if you duplicate a connection, two signals will be emitted. You can always break a connection using disconnect().
 .PP
@@ -493,7 +493,7 @@ Dumps a tree of children to the debug output.
 .PP
 This function is useful for debugging, but does nothing if the library has been compiled in release mode (i.e. without debugging information).
 .SH "bool TQObject::event ( TQEvent * e )\fC [virtual]\fR"
-This virtual function receives events to an object and should return TRUE if the event \fIe\fR was recognized and processed.
+This virtual function receives events to an object and should return true if the event \fIe\fR was recognized and processed.
 .PP
 The event() function can be reimplemented to customize the behavior of an object.
 .PP
@@ -503,7 +503,7 @@ Reimplemented in TQWidget.
 .SH "bool TQObject::eventFilter ( TQObject * watched, TQEvent * e )\fC [virtual]\fR"
 Filters events if this object has been installed as an event filter for the \fIwatched\fR object.
 .PP
-In your reimplementation of this function, if you want to filter the event \fIe\fR, out, i.e. stop it being handled further, return TRUE; otherwise return FALSE.
+In your reimplementation of this function, if you want to filter the event \fIe\fR, out, i.e. stop it being handled further, return true; otherwise return false.
 .PP
 Example:
 .PP
@@ -557,11 +557,11 @@ Example:
 .br
                 tqDebug( "Ate key press %d", k->key() );
 .br
-                return TRUE;
+                return true;
 .br
             } else {
 .br
-                return FALSE;
+                return false;
 .br
             }
 .br
@@ -579,17 +579,17 @@ Example:
 .PP
 Notice in the example above that unhandled events are passed to the base class's eventFilter() function, since the base class might have reimplemented eventFilter() for its own internal purposes.
 .PP
-\fBWarning:\fR If you delete the receiver object in this function, be sure to return TRUE. Otherwise, TQt will forward the event to the deleted object and the program might crash.
+\fBWarning:\fR If you delete the receiver object in this function, be sure to return true. Otherwise, TQt will forward the event to the deleted object and the program might crash.
 .PP
 See also installEventFilter().
 .PP
 Reimplemented in TQAccel, TQScrollView, and TQSpinBox.
 .SH "bool TQObject::highPriority () const"
-Returns TRUE if the object is a high-priority object, or FALSE if it is a standard-priority object.
+Returns true if the object is a high-priority object, or false if it is a standard-priority object.
 .PP
 High-priority objects are placed first in TQObject's list of children on the assumption that they will be referenced very often.
 .SH "bool TQObject::inherits ( const char * clname ) const"
-Returns TRUE if this object is an instance of a class that inherits \fIclname\fR, and \fIclname\fR inherits TQObject; otherwise returns FALSE.
+Returns true if this object is an instance of a class that inherits \fIclname\fR, and \fIclname\fR inherits TQObject; otherwise returns false.
 .PP
 A class is considered to inherit itself.
 .PP
@@ -599,20 +599,20 @@ Example:
 .br
         TQTimer *t = new TQTimer;         // TQTimer inherits TQObject
 .br
-        t->inherits( "TQTimer" );        // returns TRUE
+        t->inherits( "TQTimer" );        // returns true
 .br
-        t->inherits( "TQObject" );       // returns TRUE
+        t->inherits( "TQObject" );       // returns true
 .br
-        t->inherits( "TQButton" );       // returns FALSE
+        t->inherits( "TQButton" );       // returns false
 .br
 .br
         // TQScrollBar inherits TQWidget and TQRangeControl
 .br
         TQScrollBar *s = new TQScrollBar( 0 );
 .br
-        s->inherits( "TQWidget" );       // returns TRUE
+        s->inherits( "TQWidget" );       // returns true
 .br
-        s->inherits( "TQRangeControl" ); // returns FALSE
+        s->inherits( "TQRangeControl" ); // returns false
 .br
 .fi
 .PP
@@ -637,7 +637,7 @@ Installs an event filter \fIfilterObj\fR on this object. For example:
 .br
 .fi
 .PP
-An event filter is an object that receives all events that are sent to this object. The filter can either stop the event or forward it to this object. The event filter \fIfilterObj\fR receives events via its eventFilter() function. The eventFilter() function must return TRUE if the event should be filtered, (i.e. stopped); otherwise it must return FALSE.
+An event filter is an object that receives all events that are sent to this object. The filter can either stop the event or forward it to this object. The event filter \fIfilterObj\fR receives events via its eventFilter() function. The eventFilter() function must return true if the event should be filtered, (i.e. stopped); otherwise it must return false.
 .PP
 If multiple event filters are installed on a single object, the filter that was installed last is activated first.
 .PP
@@ -670,13 +670,13 @@ Here's a \fCKeyPressEater\fR class that eats the key presses of its monitored ob
 .br
             tqDebug( "Ate key press %d", k->key() );
 .br
-            return TRUE; // eat event
+            return true; // eat event
 .br
         } else {
 .br
             // standard event processing
 .br
-            return FALSE;
+            return false;
 .br
         }
 .br
@@ -703,11 +703,11 @@ And here's how to install it on two widgets:
 .PP
 The TQAccel class, for example, uses this technique to intercept accelerator key presses.
 .PP
-\fBWarning:\fR If you delete the receiver object in your eventFilter() function, be sure to return TRUE. If you return FALSE, TQt sends the event to the deleted object and the program will crash.
+\fBWarning:\fR If you delete the receiver object in your eventFilter() function, be sure to return true. If you return false, TQt sends the event to the deleted object and the program will crash.
 .PP
 See also removeEventFilter(), eventFilter(), and event().
 .SH "bool TQObject::isA ( const char * clname ) const"
-Returns TRUE if this object is an instance of the class \fIclname\fR; otherwise returns FALSE.
+Returns true if this object is an instance of the class \fIclname\fR; otherwise returns false.
 .PP
 Example:
 .PP
@@ -715,15 +715,15 @@ Example:
 .br
     TQTimer *t = new TQTimer; // TQTimer inherits TQObject
 .br
-    t->isA( "TQTimer" );     // returns TRUE
+    t->isA( "TQTimer" );     // returns true
 .br
-    t->isA( "TQObject" );    // returns FALSE
+    t->isA( "TQObject" );    // returns false
 .br
 .fi
 .PP
 See also inherits() and metaObject().
 .SH "bool TQObject::isWidgetType () const"
-Returns TRUE if the object is a widget; otherwise returns FALSE.
+Returns true if the object is a widget; otherwise returns false.
 .PP
 Calling this function is equivalent to calling inherits("TQWidget"), except that it is much faster.
 .SH "void TQObject::killTimer ( int id )"
@@ -774,14 +774,14 @@ Information about all available properties are provided through the metaObject()
 See also setProperty(), TQVariant::isValid(), metaObject(), TQMetaObject::propertyNames(), and TQMetaObject::property().
 .PP
 Example: qutlook/centralwidget.cpp.
-.SH "TQObjectList * TQObject::queryList ( const char * inheritsClass = 0, const char * objName = 0, bool regexpMatch = TRUE, bool recursiveSearch = TRUE ) const"
+.SH "TQObjectList * TQObject::queryList ( const char * inheritsClass = 0, const char * objName = 0, bool regexpMatch = true, bool recursiveSearch = true ) const"
 Searches the children and optionally grandchildren of this object, and returns a list of those objects that are named or that match \fIobjName\fR and inherit \fIinheritsClass\fR. If \fIinheritsClass\fR is 0 (the default), all classes match. If \fIobjName\fR is 0 (the default), all object names match.
 .PP
-If \fIregexpMatch\fR is TRUE (the default), \fIobjName\fR is a regular expression that the objects's names must match. The syntax is that of a TQRegExp. If \fIregexpMatch\fR is FALSE, \fIobjName\fR is a string and object names must match it exactly.
+If \fIregexpMatch\fR is true (the default), \fIobjName\fR is a regular expression that the objects's names must match. The syntax is that of a TQRegExp. If \fIregexpMatch\fR is false, \fIobjName\fR is a string and object names must match it exactly.
 .PP
 Note that \fIinheritsClass\fR uses single inheritance from TQObject, the way inherits() does. According to inherits(), TQMenuBar inherits TQWidget but not TQMenuData. This does not quite match reality, but is the best that can be done on the wide variety of compilers TQt supports.
 .PP
-Finally, if \fIrecursiveSearch\fR is TRUE (the default), queryList() searches \fIn\fRth-generation as well as first-generation children.
+Finally, if \fIrecursiveSearch\fR is true (the default), queryList() searches \fIn\fRth-generation as well as first-generation children.
 .PP
 If all this seems a bit complex for your needs, the simpler child() function may be what you want.
 .PP
@@ -802,7 +802,7 @@ This somewhat contrived example disables all the buttons in this window:
 .br
         ++it;
 .br
-        ((TQButton*)obj)->setEnabled( FALSE );
+        ((TQButton*)obj)->setEnabled( false );
 .br
     }
 .br
@@ -840,7 +840,7 @@ Sets the object's name to \fIname\fR.
 .SH "bool TQObject::setProperty ( const char * name, const TQVariant & value )\fC [virtual]\fR"
 Sets the value of the object's \fIname\fR property to \fIvalue\fR.
 .PP
-Returns TRUE if the operation was successful; otherwise returns FALSE.
+Returns true if the operation was successful; otherwise returns false.
 .PP
 Information about all available properties is provided through the metaObject().
 .PP
@@ -848,7 +848,7 @@ See also property(), metaObject(), TQMetaObject::propertyNames(), and TQMetaObje
 .PP
 Example: qutlook/centralwidget.cpp.
 .SH "bool TQObject::signalsBlocked () const"
-Returns TRUE if signals are blocked; otherwise returns FALSE.
+Returns true if signals are blocked; otherwise returns false.
 .PP
 Signals are not blocked by default.
 .PP