Author: matt
Date: 2009-06-30 06:57:45 -0700 (Tue, 30 Jun 2009)
New Revision: 6808
Log:
Typos.
Modified:
branches/branch-1.3/test/unittest_about.cxx
Modified: branches/branch-1.3/test/unittest_about.cxx
===================================================================
--- branches/branch-1.3/test/unittest_about.cxx 2009-06-30 13:38:52 UTC (rev
6807)
+++ branches/branch-1.3/test/unittest_about.cxx 2009-06-30 13:57:45 UTC (rev
6808)
@@ -38,6 +38,9 @@
About(int x, int y, int w, int h) : Fl_Help_View(x, y, w, h) {
value(
"<htmL><body><h2>About Unit Testing...</h2>\n"
+"The Unit Testing application can be used to verify correct graphis rendering "
+"on the current platform. The core developer team uses this program to make
sure that the "
+"FLTK user experience is identical on all supprted graphics systems."
"<h3>the UI Designer</h3>\n"
"<p>Designing a good user interface is an art. Widgets must be selected and
carefully positioned "
"to create a consistent look and feel for the user. Text must fit into given
boxes and graphic "
@@ -51,7 +54,7 @@
"in the same order in which a new graphics driver could be implemented. Most
tests rely "
"on the previous test to function correctly, so sticking to the given order is
a good idea.</p>\n"
"<h3>Conventions</h3>\n"
-"<p>In most tests, two layers of graphics are drawn for most test. The lower
layer contains "
+"<p>Two layers of graphics are drawn for most test. The lower layer contains "
"red and green pixels. The upper layer contains black pixels. The test is
rendered correctly "
"if all red pixels are covered, but none of the green pixels. The top graphics
layer can be "
"switched on and off.</p>"
_______________________________________________
fltk-commit mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-commit
