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

Fixed odd Listbox sizing on Windows. (Windows by default sizes List Box controls so that partial items are not visible.)

This commit is contained in:
Pietro Gagliardi 2014-04-02 10:15:04 -04:00
parent 3fe4c2f113
commit 973853c835
3 changed files with 6 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
controlcandidates.md
View File

@ -21,8 +21,6 @@ WINDOWS
- OpenGL: http://msdn.microsoft.com/en-us/library/windows/desktop/dd374379%28v=vs.85%29.aspx - OpenGL: http://msdn.microsoft.com/en-us/library/windows/desktop/dd374379%28v=vs.85%29.aspx
- don't use ES_NUMBER for number-only text boxes, as "it is still possible to paste non-digits into the edit control." (though a commenter on MSDN says that's wrong?) - don't use ES_NUMBER for number-only text boxes, as "it is still possible to paste non-digits into the edit control." (though a commenter on MSDN says that's wrong?)
- might want to just have spinners and not numeric text boxes??? - might want to just have spinners and not numeric text boxes???
- TODO
- add LBS_NOINTEGRALHEIGHT to our regular listboxes?
GTK+ GTK+
- GtkCalendar for date selection (TODO doesn't handle times) - GtkCalendar for date selection (TODO doesn't handle times)

5
sysdata_windows.go
View File

@ -87,9 +87,10 @@ var classTypes = [nctypes]*classData{
name: "LISTBOX", name: "LISTBOX",
// TODO also _WS_HSCROLL? // TODO also _WS_HSCROLL?
// we don't use _LBS_STANDARD because it sorts // we don't use _LBS_STANDARD because it sorts
style: _LBS_NOTIFY | _WS_BORDER | _WS_VSCROLL | controlstyle, // _LBS_NOINTEGRALHEIGHT gives us exactly the size we want
style: _LBS_NOTIFY | _WS_BORDER | _LBS_NOINTEGRALHEIGHT | _WS_VSCROLL | controlstyle,
xstyle: 0 | controlxstyle, xstyle: 0 | controlxstyle,
altStyle: _LBS_EXTENDEDSEL | _LBS_NOTIFY | _WS_BORDER | _WS_VSCROLL | controlstyle, altStyle: _LBS_EXTENDEDSEL | _LBS_NOTIFY | _LBS_NOINTEGRALHEIGHT | _WS_BORDER | _WS_VSCROLL | controlstyle,
appendMsg: _LB_ADDSTRING, appendMsg: _LB_ADDSTRING,
insertBeforeMsg: _LB_INSERTSTRING, insertBeforeMsg: _LB_INSERTSTRING,
deleteMsg: _LB_DELETESTRING, deleteMsg: _LB_DELETESTRING,

6
todo.md
View File

@ -5,8 +5,8 @@ so I don't forget:
- character-limited entry fields, numeric entry fields, multiline entry fields - character-limited entry fields, numeric entry fields, multiline entry fields
- possible rename of LineEdit? - possible rename of LineEdit?
- especially for password fields - NewPasswordEntry()? - especially for password fields - NewPasswordEntry()?
- [Mac OS X] Listbox should have a border style - [all platforms] Listbox should have a border style
- [Windows] a different border on LineEdits and Listboxes? - [Windows] a different border on LineEdits and Listboxes
- padding and spacing in Stack - padding and spacing in Stack
- allow Combobox to have initial settings - allow Combobox to have initial settings
- Combobox and Listbox insertions and deletions should allow bulk (...string) - Combobox and Listbox insertions and deletions should allow bulk (...string)
@ -43,7 +43,7 @@ important things:
- make gcc (Unix)/clang (Mac OS X) pedantic about warnings/errors; also -Werror - make gcc (Unix)/clang (Mac OS X) pedantic about warnings/errors; also -Werror
- make sure scrollbars in Listbox work identically on all platforms (specifically the existence and autohiding of both horizontal and vertical scrollbars) - make sure scrollbars in Listbox work identically on all platforms (specifically the existence and autohiding of both horizontal and vertical scrollbars)
- pin down this behavior; also note non-editability - pin down this behavior; also note non-editability
- the size of Listboxes on Windows does not fill the requested space completely (wait, wasn't there a style that governed this?) - listboxes spanning the vertical height of the window don't always align with the bottom border of the edit control attached to the bottom of the window...
- make sure mouse events don't trigger if the control size is larger than the Area size and the mouse event happens outside the Area range on all platforms - make sure mouse events don't trigger if the control size is larger than the Area size and the mouse event happens outside the Area range on all platforms
super ultra important things: super ultra important things: