From 2e869615d35f36462ab3978b2e518d91a1633770 Mon Sep 17 00:00:00 2001 From: Pietro Gagliardi Date: Sat, 1 Mar 2014 15:23:49 -0500 Subject: [PATCH] Documentation and TODO changes. --- init.go | 2 +- todo.md | 9 ++------- 2 files changed, 3 insertions(+), 8 deletions(-) diff --git a/init.go b/init.go index a47266c..56b4571 100644 --- a/init.go +++ b/init.go @@ -2,7 +2,7 @@ package ui // Go sets up the UI environment and runs main in a goroutine. -// If initialization fails, Go returns an error. +// If initialization fails, Go returns an error and main is not called. // Otherwise, Go does not return to its caller until (unless? TODO) the application loop exits, at which point it returns nil. // // This model is undesirable, but Cocoa limitations require it. diff --git a/todo.md b/todo.md index 7b6ffbc..9558d8c 100644 --- a/todo.md +++ b/todo.md @@ -23,6 +23,8 @@ so I don't forget: - ensure MsgBoxError can run if initialization failed if things change ever important things: +- ui.Go() should exit when the main() you pass in exits +- because the main event loop is not called if initialization fails, it is presently impossible for MsgBoxError() to work if UI initialization fails; this basically means we cannot allow initializiation to fail on Mac OS X if we want to be able to report UI init failures to the user with one - there's no GTK+ error handling whatsoever; we need to figure out how it works - make sure GTK+ documentation point differences don't matter - button sizes and LineEdit sizes on Windows seem too big; Comboboxes have margins @@ -55,11 +57,4 @@ far off: maybe: - rename Stack to Box? - make Combobox and Listbox satisfy sort.Interface? -- this: -``` -[16:27] pietro10: depends what you mean by safe -[16:27] pietro10: sounds like you should move this functionality into a function though. -[16:28] (so the user can decide what to do with the error) -[16:28] typically people don't like their libraries calling exit :) -``` - indeterminate progress bars (not supported on Windows 2000)