summaryrefslogtreecommitdiff
path: root/uitask_windows.go
AgeCommit message (Collapse)Author
2014-03-05Have ui.Go() return on main() return on Windows.Pietro Gagliardi
2014-03-01Major code restructure to allow Cocoa to work correctly. Cocoa requires that ↵Pietro Gagliardi
the application loop run on the very first OS thread created, not just an any ordinary thread. To support this, your code must now be run by the UI init code. Windows and Unix builds still work fine; Mac OS X fails for reasons I now have to debug.
2014-02-19Got rid of my Windows input lag problems on Windows (triggered by the switch ↵Pietro Gagliardi
to the concurrent garbage collector sweep routine in the Go runtime) by treating <-uitask as a Windows message itself posted to the message loop thread and not making the message loop a CPU waster.
2014-02-19Moved to a proper package; main() is now a test and go test -c is used to ↵Pietro Gagliardi
build. Once I iron out a bug with Windows event handling, I'll add a README.
2014-02-17Removed all //package ui comments.Pietro Gagliardi
2014-02-15More error/TODO reduction.Pietro Gagliardi
2014-02-11Fixed the PeekMessage() call as per ↵Pietro Gagliardi
http://blogs.msdn.com/b/oldnewthing/archive/2006/02/10/529525.aspx
2014-02-11Fixed the wndproc not responding: turns out I have to have message dispatch ↵Pietro Gagliardi
in the UI thread...
2014-02-11All build errors resolved. Now to test...Pietro Gagliardi
2014-02-11Locked the Windows message loop goroutine to the OS thread.Pietro Gagliardi
2014-02-11Added the Windows message loop.Pietro Gagliardi
2014-02-11Set up initialization on Windows (2/2).Pietro Gagliardi
2014-02-11Started implementing the public API: added the Window and Control types and ↵Pietro Gagliardi
the skeleton of the Windows implementation.