More future plans and TODOs.

futureplans.md

@@ -44,6 +44,8 @@ style changes:
 			- I think this is a platform behavior...
 	- should field descriptions in method comments include the receiver name? (for instance e.Held vs. Held) - see what Go's own documentation does
 	- need to figure out exactly how to indicate that a struct{}{} is sent on an event channel (I use about six or so different wordings so far...)
+	- "package ui", "the package"
+		- also "library" both in docs and comments and code, etc.
 - make passing of parameters and type conversions of parameters to uitask on Windows consistent: explicit _WPARAM(xxx)/_LPARAM(xxx)/uintptr(xxx), for example
 	- do this for type signatures in exported functions: (err error) or just error?
 	- do this for the names of GTK+ helper functions (gtkXXX or gXXX)
@@ -57,7 +59,7 @@ far off:
 	- http://blogs.msdn.com/b/oldnewthing/archive/2003/10/21/55384.aspx
 - rename Stack to Box?
 - maybe change multiple selection lists to checkbox lists?
-	- windows HIG refernece: ???
+	- windows HIG refernece: http://msdn.microsoft.com/en-us/library/windows/desktop/aa511485.aspx - conflicting, confusing info
 	- gtk+ HIG reference: https://developer.gnome.org/hig-book/3.4/controls-lists.html.en
 	- mac HIG reference: ???
 - go over the old new thing's scrollbar series to make sure I'm doing everything right with scrollbars in Windows Areas

sysdata_windows.go

@@ -90,6 +90,7 @@ var classTypes = [nctypes]*classData{
 		// TODO also _WS_HSCROLL?
 		// we don't use _LBS_STANDARD because it sorts (and has WS_BORDER; see above)
 		// _LBS_NOINTEGRALHEIGHT gives us exactly the size we want
+		// TODO say why we don't use LBS_MULTISEL (listbox docs and http://msdn.microsoft.com/en-us/library/windows/desktop/aa511485.aspx)
 		style:			_LBS_NOTIFY | _LBS_NOINTEGRALHEIGHT | _WS_VSCROLL | controlstyle,
 		xstyle:			_WS_EX_CLIENTEDGE | controlxstyle,
 		altStyle:			_LBS_EXTENDEDSEL | _LBS_NOTIFY | _LBS_NOINTEGRALHEIGHT | _WS_VSCROLL | controlstyle,