diff options
| author | Pietro Gagliardi <[email protected]> | 2014-07-02 20:24:10 -0400 |
|---|---|---|
| committer | Pietro Gagliardi <[email protected]> | 2014-07-02 20:24:10 -0400 |
| commit | 4dd5ceb11d62bd6b9af4847936314a9d8c45707f (patch) | |
| tree | 2d16a5a11d7790a5b2d53a2d255b31db8e5ce1a1 | |
| parent | 8c5030b7f7809de30997acaed0a6288286717c21 (diff) | |
More new plans.
| -rw-r--r-- | newplan | 8 |
1 files changed, 8 insertions, 0 deletions
@@ -59,3 +59,11 @@ sending a message across threads will hang up the first thread during the send i GENERAL NOTES what about spinning an inner message pump during each event and run event handlers in their own goroutine? no, still subject to the same race condition that could lead to a double button press +another caveat I neve rnoticed before + [20:20] <andlabs> ,..ack + [20:20] <andlabs> I just realized osmething else about my API design + [20:21] <andlabs> I can't stop preemption during an event handle + [20:21] <andlabs> r + [20:23] <andlabs> no matter how I slice it I might have to have tow different sets of funcitons + [20:23] <andlabs> one for outside evernts and one for inside events + [20:23] <andlabs> yuck |