Put the Label that changed each second in the main test.

README.md

@@ -9,7 +9,7 @@ The issue:
 - this fools Go's deadlock detector; it never reports anything
 - changing from standard mutexes to R/W mutexes does not work
 - making resizes concurrent causes resizes to become too slow to be acceptable (they trail behind the actual user resizing by a significant amount)
-If you know a better way I can do things, **please** help... I'm at my wits end here<br>`test/test -area` will run the Area test with the ticking label; I should probably add one to the main test so it can be tested on all platforms...
+If you know a better way I can do things, **please** help... I'm at my wits end here<br>The main test (`test/test`) now has its label show the current time; GTK+ users can run `test/test -area` for the Area test that sparked this whole calamity.
 
 
 

test/main.go

@@ -243,9 +243,13 @@ func myMain() {
 		}
 	}
 
+	ticker := time.Tick(time.Second)
+
 mainloop:
 	for {
 		select {
+		case curtime := <-ticker:
+			l.SetText(curtime.String())
 		case <-w.Closing:
 			break mainloop
 		case <-b.Clicked: