interesting
/
andlabs-ui
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

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

This commit is contained in:
Pietro Gagliardi 2014-04-13 16:46:22 -04:00
parent 7a436e8bd3
commit e4c27a4a72
3 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
futureplans.md
View File

@ -88,6 +88,7 @@ big things:
- http://msdn.microsoft.com/en-us/library/windows/desktop/ms633541%28v=vs.85%29.aspx - 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) - 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 - 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: 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 - 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

2
test/main.go
View File

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

5
todo.md
View File

@ -1,9 +1,10 @@
important things: 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) - 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 - 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 - area test time label weirdness - this indicates bugs in Stack
- does not show anything past the date on windows - 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 - 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: super ultra important things:
- window sizes are inconsistent and wrong: we need to see on which platforms the titlebars/borders/etc. count... - window sizes are inconsistent and wrong: we need to see on which platforms the titlebars/borders/etc. count...