changeset 1456:f1a4a6efe1f1

documentation: update references to LinkReceiver
author corvid <corvid@lavabit.com>
date Mon, 30 Nov 2009 20:18:34 +0000
parents 193c0699f16a
children 73d21d6151ae
files dw/image.hh dw/selection.hh dw/textblock.hh
diffstat 3 files changed, 10 insertions(+), 10 deletions(-) [+]
line wrap: on
line diff
--- a/dw/image.hh	Mon Nov 30 20:09:42 2009 +0000
+++ b/dw/image.hh	Mon Nov 30 20:18:34 2009 +0000
@@ -68,7 +68,7 @@
  * <h3>Signals</h3>
  *
  * For image maps, dw::Image uses the signals defined in
- * dw::core::Widget::LinkReceiver. For client side image maps, -1 is
+ * dw::core::Layout::LinkReceiver. For client side image maps, -1 is
  * passed for the coordinates, for server side image maps, the respective
  * coordinates are used. See section "Image Maps" below.
  *
@@ -89,7 +89,7 @@
  *
  * dw::ImageMapsList::addShapeToCurrentMap adds a shape to the current
  * map. The \em link argument is a number, which is later passed to
- * the dw::core::Widget::LinkReceiver.
+ * the dw::core::Layout::LinkReceiver.
  *
  * This map list is then, together with the key for the image, passed to
  * dw::Image::setUseMap. For HTML, a URL with the value of the "ismap"
@@ -109,7 +109,7 @@
  * To use images for server side image maps, you must call
  * dw::Image::setIsMap, and the dw::Image::style must contain a valid link
  * (dw::core::style::Style::x_link). After this, motions and clicks are
- * delegated to dw::core::Widget::LinkReceiver.
+ * delegated to dw::core::Layout::LinkReceiver.
  *
  * \sa\ref dw-images-and-backgrounds
  */
--- a/dw/selection.hh	Mon Nov 30 20:09:42 2009 +0000
+++ b/dw/selection.hh	Mon Nov 30 20:18:34 2009 +0000
@@ -40,7 +40,7 @@
  *                                          within the iterator,
  * <tr><td>int linkNo                   <td>if this item is associated with a
  *                                          link, its number (see
- *                                          dw::core::Widget::LinkReceiver),
+ *                                          dw::core::Layout::LinkReceiver),
  *                                          otherwise -1
  * <tr><td>dw::core::EventButton *event <td>the event itself; only the button
  *                                          is used
@@ -69,12 +69,12 @@
  *
  * The return value is the same as in DwWidget event handling methods.
  * I.e., in most cases, they should simply return it. The events
- * dw::core::Widget::LinkReceiver::press,
- * dw::core::Widget::LinkReceiver::release and
- * dw::core::Widget::LinkReceiver::click (but not
- * dw::core::Widget::LinkReceiver::enter) are emitted by these methods, so
+ * dw::core::Layout::LinkReceiver::press,
+ * dw::core::Layout::LinkReceiver::release and
+ * dw::core::Layout::LinkReceiver::click (but not
+ * dw::core::Layout::LinkReceiver::enter) are emitted by these methods, so
  * that widgets which let dw::core::SelectionState handle links, should only
- * emit dw::core::Widget::LinkReceiver::enter for themselves.
+ * emit dw::core::Layout::LinkReceiver::enter for themselves.
  *
  * <h3>Selection State</h3>
  *
--- a/dw/textblock.hh	Mon Nov 30 20:09:42 2009 +0000
+++ b/dw/textblock.hh	Mon Nov 30 20:18:34 2009 +0000
@@ -13,7 +13,7 @@
  * <h3>Signals</h3>
  *
  * dw::Textblock uses the signals defined in
- * dw::core::Widget::LinkReceiver, related to links. The coordinates are
+ * dw::core::Layout::LinkReceiver, related to links. The coordinates are
  * always -1.
  *
  *