[gtkmm] Documentation: Don't mention non-existant Gdk::Colormap class.



commit 0b6477ff2168bc8dc684a3dcbeae25e70ca5cbc0
Author: Murray Cumming <murrayc murrayc com>
Date:   Thu Jan 13 14:47:02 2011 +0100

    Documentation: Don't mention non-existant Gdk::Colormap class.
    
    * gdk/src/color.hg:
    * gdk/src/screen.hg:
    * gdk/src/types.hg:
    * gdk/src/visual.hg: Remove mentions of Colormap, which no longer exists
    and which doesn't seem to need any replacement.

 ChangeLog         |   10 ++++++++++
 gdk/src/color.hg  |    4 +---
 gdk/src/screen.hg |    3 +--
 gdk/src/types.hg  |    3 ---
 gdk/src/visual.hg |    9 +--------
 5 files changed, 13 insertions(+), 16 deletions(-)
---
diff --git a/ChangeLog b/ChangeLog
index 3436e85..afa8011 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,13 @@
+2011-01-13  Murray Cumming  <murrayc murrayc com>
+
+	Documentation: Don't mention non-existant Gdk::Colormap class.
+
+	* gdk/src/color.hg:
+	* gdk/src/screen.hg:
+	* gdk/src/types.hg:
+	* gdk/src/visual.hg: Remove mentions of Colormap, which no longer exists 
+	and which doesn't seem to need any replacement.
+
 2011-01-11  Kjell Ahlstedt  <kjell ahlstedt bredband net>
 
   Widget::set_window(): Increase the ref count of the Gdk::Window.
diff --git a/gdk/src/color.hg b/gdk/src/color.hg
index 12faa94..70ee4df 100644
--- a/gdk/src/color.hg
+++ b/gdk/src/color.hg
@@ -45,12 +45,11 @@ public:
   _CUSTOM_DEFAULT_CTOR
 
   /** Instantiate a new Gdk::Color.
-   * You should then use the set methods and call Gdk::Colormap::alloc_color().
+   * You should then use the set methods.
    */
   Color();
 
   /** Instantiate a new Gdk::Color.
-   * The color is not allocated - you must call Gdk::Colormap::alloc_color() yourself.
    * The text string can be in any of the forms accepted by XParseColor; these include names for a color from rgb.txt,
    * such as DarkSlateGray, or a hex specification such as 305050.
    * @param value the string specifying the color..
@@ -81,7 +80,6 @@ public:
   void set_hsl(double h, double s, double l);
 
   /** Parses a textual specification of a color and fills in the red, green, and blue values.
-  * The color is not allocated - you must call Gdk::Colormap::alloc_color() yourself.
   * The text string can be in any of the forms accepted by XParseColor; these include names for a color from rgb.txt,
   * such as DarkSlateGray, or a hex specification such as 305050.
   *
diff --git a/gdk/src/screen.hg b/gdk/src/screen.hg
index 0ae8dbd..7a6a6e5 100644
--- a/gdk/src/screen.hg
+++ b/gdk/src/screen.hg
@@ -35,11 +35,10 @@ class Display;
 class Visual;
 class Window;
 
-//TODO: Remove mentino of Colormap:
 /** Object representing a physical screen
  * Gdk::Screen objects are the GDK representation of a physical screen. It is used throughout GDK and GTK+ to specify
  * which screen the top level windows are to be displayed on. It is also used to query the screen specification and
- * default settings such as the default colormap (get_default_colormap()), the screen width (get_width()), etc.
+ * default settings such as the screen width (get_width()), etc.
  * Note that a screen may consist of multiple monitors which are merged to form a large screen area.
  */
 class Screen : public Glib::Object
diff --git a/gdk/src/types.hg b/gdk/src/types.hg
index 9efef53..2715530 100644
--- a/gdk/src/types.hg
+++ b/gdk/src/types.hg
@@ -53,9 +53,6 @@ enum { ERROR = GTKMM_MACRO_DEFINITION_ERROR };
 namespace Gdk
 {
 
-class Bitmap;
-class Colormap;
-class Pixmap;
 class Window;
 class Font;
 class Color;
diff --git a/gdk/src/visual.hg b/gdk/src/visual.hg
index 429bf85..c25b2c0 100644
--- a/gdk/src/visual.hg
+++ b/gdk/src/visual.hg
@@ -42,14 +42,7 @@ _WRAP_ENUM(VisualType, GdkVisualType)
  * formats; for example the "red" element of an RGB pixel may be in the top 8 bits of the pixel, or may be in the lower 4
  * bits.
  *
- * Usually you can avoid thinking about visuals in GTK+. Visuals are useful to interpret the contents of a GdkImage, but
- * you should avoid Gdk::Image precisely because its contents depend on the display hardware; use Gdk::Pixbuf instead, for
- * all but the most low-level purposes. Also, anytime you provide a Gdk::Colormap, the visual is implied as part of the
- * colormap (Gdk::Colormap::get_visual()), so you won't have to provide a visual in addition.
- *
- * There are several standard visuals. The visual returned by get_system() is the system's default visual. get_visual()
- * returns the visual most suited to displaying full-color image data. If you use the calls in Gdk::RGB, you should create
- * your windows using this visual (and the colormap returned by Gdk::Rgb::get_colormap()).
+ * There are several standard visuals. The visual returned by Gdk::Screen::get_system_visual() is the system's default visual.
  *
  * A number of methods are provided for determining the "best" available visual. For the purposes of making this
  * determination, higher bit depths are considered better, and for visuals of the same bit depth, GDK_VISUAL_PSEUDO_COLOR



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]