summaryrefslogtreecommitdiffstats
path: root/doc/html/designer-manual-4.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/designer-manual-4.html')
-rw-r--r--doc/html/designer-manual-4.html2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/html/designer-manual-4.html b/doc/html/designer-manual-4.html
index fd642a9d..17b27fcf 100644
--- a/doc/html/designer-manual-4.html
+++ b/doc/html/designer-manual-4.html
@@ -201,7 +201,7 @@ body { background: #ffffff; color: black; }
}
}
</pre>
- <p>The code for this function is tquite long, but it isn't difficult. We start by setting a default color to white. If there are any colors in the <tt>m_colors</tt> map we set the default color to be the current color showing in the current view. We then invoke TQt's static <a href="qcolordialog.html#getColor">getColor()</a> dialog, passing it the default color. (If the user cancels an invalid color is returned.)</p>
+ <p>The code for this function is quite long, but it isn't difficult. We start by setting a default color to white. If there are any colors in the <tt>m_colors</tt> map we set the default color to be the current color showing in the current view. We then invoke TQt's static <a href="qcolordialog.html#getColor">getColor()</a> dialog, passing it the default color. (If the user cancels an invalid color is returned.)</p>
<p>If the user chose a color we want to show their chosen color in our custom dialog, so we create a pixmap and fill it with their chosen color. We create an instance of our ColorNameForm as a modal dialog (third argument is TRUE). We then call its <tt>setColors()</tt> function to set the colors in the <tt>m_colors</tt> map (so that the <tt>validate()</tt> function will work correctly). We set its colorLabel's pixmap to the pixmap we've just created, i.e. to a rectangle in the user's chosen color.</p>
<p>We execute (<tt>exec()</tt>) the dialog. If the user clicks OK (and the color name they've entered is valid), the call will return a true value. In this case we retrieve the name they've entered from the line edit and create a new entry in the <tt>m_colors</tt> map using the name the user has given and the color they chose.</p>
<p>At this point we could simply mark the views "dirty" and call repopulate. Instead we'll add the new color to each view directly and save the overhead of a full update (which might be considerable if we have thousands of colors).</p>