{"push_id":2129351309,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"6ae48b0da432f7ffb2b93312443a4f81f2ced4b0","before":"be49761772febd42c5563179942144bcbc143c85","commits":[{"sha":"6ae48b0da432f7ffb2b93312443a4f81f2ced4b0","author":{"name":"WammKD","email":"e507594289949c214c4ccff5f234fab467613063@outlook.com"},"message":"I don't remember if I committed the changes but I tried using atomics earlier; I was setting the box in the let in `set-display` so it kept overwriting the value. It's better this way since I think, the first time, I was using it for blocking or some such. This way, the new thread can be completely dedicated to displaying the `playWindow` while the other handles waiting for user input. Waiting for one second isn't too quick a pace to call MPD and the other needn't do it except to play songs or the like. This avoids issues like the thread crashing from calling MPD too quickly; I solved the issue of the sock to MPD being closed by passing the thread its own client. And clearing the window and rewriting the status is solved by doing it in the original thread. All three of the original issues are solved with no flickering of the display and no ginning up 100 threads. It's looking good. Memory is still good and CPU is what it was. That should go down with some changes. It's fluctuating between 2% and 4% which is worse than CMUS's generally consistent 2% but not by much, which is good. Restructuring the method to not always call MPD for the song every time (when paused or stopped) should fix that. I can probably remove the loop parameter from `set-display`, too. Looking good, thus far.","distinct":true,"url":"https://api.github.com/repos/WammKD/guile-mizik/commits/6ae48b0da432f7ffb2b93312443a4f81f2ced4b0"}]}
{"actor":{"display_login":"WammKD"}}