From 13229d689ceb4d11d6d8c61691df2caa00406cd0 Mon Sep 17 00:00:00 2001
From: Adam Mitz <mitza-oci@users.noreply.github.com>
Date: Fri, 19 Feb 2010 15:21:42 +0000
Subject: adding documentation for the Define_Custom inheritance feature

---
 docs/README                       | 5 +++++
 docs/html/MakeProjectCreator.html | 6 ++++++
 2 files changed, 11 insertions(+)

diff --git a/docs/README b/docs/README
index ad67a3c9..3a23de4a 100644
--- a/docs/README
+++ b/docs/README
@@ -437,6 +437,11 @@ information about how to process the input files and what output files are
 created.  Once the custom file type is defined, MOC_Files can be defined in
 order to specify the input files for this new file type.
 
+Define_Custom definitions may use single inheritance.  This is useful for
+creating aliased names:
+  Define_Custom(QtMOC) : MOC {
+  }
+
 Here is a list of keywords that can be used within the scope of
 Define_Custom or Modify_Custom:
 
diff --git a/docs/html/MakeProjectCreator.html b/docs/html/MakeProjectCreator.html
index 802ef252..5757bacb 100644
--- a/docs/html/MakeProjectCreator.html
+++ b/docs/html/MakeProjectCreator.html
@@ -2969,6 +2969,12 @@
               <em class="Code">MOC_Files</em> can be used to specify the
               input files for this new file type.</li>
 
+              <li class="Body">Define_Custom definitions may use single
+              inheritance.  This is useful for creating aliased names:
+              <p class="Code">Define_Custom(QtMOC) : MOC {</p>
+              <p class="Code">}</p>
+              </li>
+
               <li class="Body">The following table contains the keywords that
               can be used within the scope of <em class=
               "Code">Define_Custom</em>.</li>
-- 
cgit v1.2.1