| Age | Commit message (Collapse) | Author |
|---|
|
our_idle_callback() and its associated stuff.
|
|
|
|
future panics caused by Go and GTK+ racing by doing the pulsing all on GTK+.
|
|
no longer work; this will be fixed soon.
|
|
on the Windows backend.
|
|
|
|
|
|
|
|
|
|
|
|
callbacks rather than using a window handler, but other than that... yeah.
|
|
|
|
|
|
passed into it, rather than a channel that sends the function to another dispatcher. Windows lets us, since SendMessage() will switch threads if called form another thread. This gets rid of one goroutine and makes things cleaner. Mac OS X has the same optimization avaialble (performSelectorOnMainThread:); GTK+... doesn't seem to...
|
|
uitask to avoid needing to deal with channels and it's the only thing using uimsg now.
|
|
|
|
|
|
|
|
This will also allow me to evaluate what happens if message boxes that are parented are closed in non-reverse order.
|
|
|
|
to fix dialogs before I can push anything.
|
|
|
|
|
|
|
|
olddocs/ since it's now being implemented.
|
|
wait for the answer to my Stack Overflow question so I can migrate dialog_darwin.go...
|
|
|
|
|
|
|
|
Windows since I can't reproduce the weird behavior anymore; I guess the new code fixes it.
|
|
I want on Mac OS X - http://stackoverflow.com/questions/24468620/how-do-i-create-a-nested-run-loop-after-nsalert-beginsheetmodalforwindow-tha - Now to see if Windows works...
|
|
|
|
out what I'm going to do about dialog modality... ugh.
|
|
|
|
|
|
|
|
|
|
is, however, getting in the way...
|
|
|
|
|
|
|
|
|
|
migrated as well.
|
|
APIs; they won't be needed anymore.
|
|
|
|
|
|
|
|
|
|
|
|
|
