Fixed weird Area time label truncation on Windows; more TODOs and future plans related to that.

futureplans.md

@@ -88,6 +88,7 @@ big things:
 			- http://msdn.microsoft.com/en-us/library/windows/desktop/ms633541%28v=vs.85%29.aspx
 				- don't worry about UI state messages yet; this is before opening the UI anyway (these might be needed when we add tab stops)
 			- http://msdn.microsoft.com/en-us/library/windows/desktop/ms644898%28v=vs.85%29.aspx GWLP_ID
+- preferred sizes in general are awkward: on Windows, no text-based size calculation is performed, so we have weird things like Labels always having the same width (so if you place a Label in a Stack by itself and forget to make it stretchy, it'll be truncated on Windows (but not on GTK+ or OS X?!))
 
 big dumb things:
 - for our two custom window classes on Windows, we should allocate extra space in the window class's info structure and then use SetWindowLongPtrW() during WM_CREATE to store the sysData and not have to make a new window class each time; this might also fix the s != nil && s.hwnd != 0 special cases in the Area WndProc if done right

test/main.go

@@ -206,7 +206,7 @@ func areaTest() {
 	sizeStack.SetStretchy(1)
 	sizeStack.SetStretchy(2)
 	layout := NewVerticalStack(a,
-		NewHorizontalStack(timedisp),
+		timedisp,
 		sizeStack)
 	layout.SetStretchy(0)
 	err = w.Open(layout)

todo.md

@@ -1,9 +1,10 @@
 important things:
 - NSComboBox scans the entered text to see if it matches one of the items and returns the index of that item if it does; find out how to suppress this so that it returns -1 unless the item was chosen from the list (like the other platforms)
 - make sure mouse events trigger when we move the mouse over an Area with a button held on OS X
-- area test time label weirdness
-	- does not show anything past the date on windows
+- area test time label weirdness - this indicates bugs in Stack
+	- does not show full time initally on Windows; it does after you resize the window
 	- does not show initially on OS X; it shows up once you resize, and even shows up after you resize back to the original size
+		- I think both bugs and the GTK+ Wayland bug below are related...
 
 super ultra important things:
 - window sizes are inconsistent and wrong: we need to see on which platforms the titlebars/borders/etc. count...