48 lines
3.3 KiB
Markdown
48 lines
3.3 KiB
Markdown
ALL:
|
|
- vertical alignment of labels still has some flaws
|
|
- gtk+: currently requires labels to be filling for this to work: grids don't do this by default, for instance
|
|
- won't cause any issues, just an inconvenience that should be addressed
|
|
- make sure tab stop behavior for Areas makes sense, or provide a handler function
|
|
- the following seems weird and will not allow clean removal of the last window; think of something better?
|
|
```
|
|
case ui.Closing:
|
|
*(d.(*bool)) = true
|
|
ui.Stop <- struct{}{}
|
|
```
|
|
- implement the concept of closing a window (which renders it unavilable for future use) and make it part of the Closing documentation
|
|
- make sure message boxes can be closed in arbitrary order meaningfully
|
|
- windows: the first message box closing will destroy the window properly and reenable the parent, but the actual call to MessageBox() won't return until the second dialog does
|
|
- docs don't say anything about threads but implies you can't call MessageBox() from a different thread
|
|
- GTK+: ???
|
|
- OS X: ???
|
|
- describe the thread safety of Window (needs to clarify construct, create, open, close, show, hide first)
|
|
|
|
MAC OS X:
|
|
- 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)
|
|
- asked: http://stackoverflow.com/questions/23046414/cocoa-how-do-i-get-nscombobox-indexofselecteditem-to-return-1-if-the-user-m
|
|
- make sure Areas get keyboard focus when clicking outside the actual Area space on Mac OS X
|
|
- http://stackoverflow.com/questions/24102367/how-do-i-make-it-so-clicking-outside-the-actual-nsview-in-a-nsscrollview-but-wit
|
|
- on initially starting the Area test, layout is totally wrong
|
|
- probably use fittingSize instead of sizeToFit
|
|
- use cascadeTopLeftFromPoint: for NSWindow or a similar routine
|
|
|
|
WINDOWS:
|
|
- windows: windows key handling is just wrong; figure out how to avoid (especially since Windows intercepts that key by default)
|
|
- control sizing is a MAJOR pain
|
|
- http://stackoverflow.com/questions/24130548/is-there-a-proper-way-to-get-the-preferred-size-of-windows-controls-there-are-s
|
|
- redrawing controls after a window resize on Windows does not work properly
|
|
- when adding IsDialogMessage() find out if that makes the area in the area bounds test automatically focused
|
|
- vertical alignment of labels can be wrong (I think; need to check again - TODO)
|
|
|
|
UNIX:
|
|
- figure out how to detect the alt key and mouse buttons above 5 properly for modifiers/Held[]
|
|
- http://stackoverflow.com/questions/24053012/gdk-is-there-a-way-i-can-get-if-an-arbitrary-keyval-or-mouse-button-is-down-dur
|
|
- double-check to make sure MouseEvent.Held[] is sorted on Unix after we figure out how to detect buttons above button 5
|
|
- sizing with client-side decorations (Wayland) don't work
|
|
- several people suggested connecting to size-allocate of the GtkLayout, but then I can wind up in a situation where there's extra padding or border space in the direction I resized
|
|
- [12:55] <myklgo> pietro10: I meant to mention: 1073): Gtk-WARNING **: Theme parsing error: gtk.css:72:20: Not using units is deprecated. Assuming 'px'. twice.
|
|
- figure out why Page Up/Page Down does tab stops
|
|
|
|
ALL PLATFORMS:
|
|
- windows code presently wraps entire function bodies in uitask; make sure the other platforms do too
|