andlabs-ui/todo.md

3.3 KiB

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:

WINDOWS:

UNIX:

  • figure out how to detect the alt key and mouse buttons above 5 properly for modifiers/Held[]
  • 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] 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