summaryrefslogtreecommitdiff
path: root/FL/Fl.H
diff options
context:
space:
mode:
authorMatthias Melcher <fltk@matthiasm.com>2009-04-19 12:47:36 +0000
committerMatthias Melcher <fltk@matthiasm.com>2009-04-19 12:47:36 +0000
commit03ec459eb03b18c4792c9edc5f8e585653c276e9 (patch)
treeff1f75585b32c98dfa21d94030f496ac3a5eaa29 /FL/Fl.H
parentb1ba38da6033889ecaff0c1f69b872fb6c76d961 (diff)
Removed extra \\c from the Doxygen documentation.
git-svn-id: file:///fltk/svn/fltk/branches/branch-1.3@6771 ea41ed52-d2ee-0310-a9c1-e6b18d33e121
Diffstat (limited to 'FL/Fl.H')
-rw-r--r--FL/Fl.H32
1 files changed, 16 insertions, 16 deletions
diff --git a/FL/Fl.H b/FL/Fl.H
index 7edc561e7..a52149f6a 100644
--- a/FL/Fl.H
+++ b/FL/Fl.H
@@ -852,29 +852,29 @@ public:
These functions support deletion of widgets inside callbacks.
- \c Fl::delete_widget() should be called when deleting widgets
- or complete widget trees (\c Fl_Group, \c Fl_Window, ...) inside
+ Fl::delete_widget() should be called when deleting widgets
+ or complete widget trees (Fl_Group, Fl_Window, ...) inside
callbacks.
The other functions are intended for internal use. The preferred
- way to use them is by using the helper class \c Fl_Widget_Tracker.
+ way to use them is by using the helper class Fl_Widget_Tracker.
The following is to show how it works ...
There are three groups of related methods:
-# scheduled widget deletion
- - \c Fl::delete_widget() schedules widgets for deletion
- - \c Fl::do_widget_deletion() deletes all scheduled widgets
+ - Fl::delete_widget() schedules widgets for deletion
+ - Fl::do_widget_deletion() deletes all scheduled widgets
-# widget watch list ("smart pointers")
- - \c Fl::watch_widget_pointer() adds a widget pointer to the watch list
- - \c Fl::release_widget_pointer() removes a widget pointer from the watch list
- - \c Fl::clear_widget_pointer() clears a widget pointer \e in the watch list
+ - Fl::watch_widget_pointer() adds a widget pointer to the watch list
+ - Fl::release_widget_pointer() removes a widget pointer from the watch list
+ - Fl::clear_widget_pointer() clears a widget pointer \e in the watch list
-# the class Fl_Widget_Tracker:
- - the constructor calls \c Fl::watch_widget_pointer()
- - the destructor calls \c Fl::release_widget_pointer()
+ - the constructor calls Fl::watch_widget_pointer()
+ - the destructor calls Fl::release_widget_pointer()
- the access methods can be used to test, if a widget has been deleted
- \see \c Fl_Widget_Tracker.
+ \see Fl_Widget_Tracker.
@{ */
// Widget deletion:
@@ -937,11 +937,11 @@ public:
/**
This class should be used to control safe widget deletion.
- You can use an \c Fl_Widget_Tracker object to watch another widget, if you
+ You can use an Fl_Widget_Tracker object to watch another widget, if you
need to know, if this widget has been deleted during a callback.
This simplifies the use of the "safe widget deletion" methods
- \c Fl::watch_widget_pointer() and \c Fl::release_widget_pointer() and
+ Fl::watch_widget_pointer() and Fl::release_widget_pointer() and
makes their use more reliable, because the destructor autmatically
releases the widget pointer from the widget watch list.
@@ -950,7 +950,7 @@ public:
scope is left. This ensures that no stale widget pointers are
left in the widget watch list (see example below).
- You can also create \c Fl_Widget_Tracker objects with \c new, but then it
+ You can also create Fl_Widget_Tracker objects with \c new, but then it
is your responsibility to delete the object (and thus remove the
widget pointer from the watch list) when it is not needed any more.
@@ -997,7 +997,7 @@ public:
<tt> if (wp.widget() == 0) // ...</tt>
- where \p wp is an \c Fl_Widget_Tracker object.
+ where \p wp is an Fl_Widget_Tracker object.
*/
int deleted() {return wp_ == 0;}
@@ -1008,7 +1008,7 @@ public:
<tt> if (wp.widget() != 0) // ...</tt>
- where \p wp is an \c Fl_Widget_Tracker object.
+ where \p wp is an Fl_Widget_Tracker object.
*/
int exists() {return wp_ != 0;}