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

More TODOs.

This commit is contained in:
Pietro Gagliardi 2014-04-02 13:48:49 -04:00
parent 150b999c0a
commit 77b5afe824
1 changed files with 1 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
todo.md
View File

@ -23,6 +23,7 @@ so I don't forget:
- will probably want to bring back Event() for this (but as NewEvent()) - will probably want to bring back Event() for this (but as NewEvent())
- add bounds checking to Area's sizing methods - add bounds checking to Area's sizing methods
- describe thread-safety of Area.SetSize() - describe thread-safety of Area.SetSize()
- should all instances of -1 as error returns from Windows functions be changed to ^0 or does the uintptr() conversion handle sign extension?
important things: important things:
- 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 (which would be desirable, maybe (would violate Windows HIG?)) - 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 (which would be desirable, maybe (would violate Windows HIG?))