Sam Hocevar

Results 189 comments of Sam Hocevar

> [e7687d4](https://github.com/cmaughan/zep/commit/e7687d4414bf786e36453efad286ca7e519d920c) Fixes the Thread one I believe? Actually, the threading issue is still not fixed. I would argue it’s a bug in `ThreadPool.hpp`: ThreadPool(size_t threads_n = std::thread::hardware_concurrency()) : stop(false)...

![image](https://user-images.githubusercontent.com/245089/51805348-7a966600-226c-11e9-919b-9c1ccd02e791.png) This is [zepto-8](https://github.com/samhocevar/zepto8), an experimental IDE for PICO-8 that I’m working on. I’m just evaluating Zep for now, but undo support and minimal Vim bindings have me thrilled! [Here](https://github.com/samhocevar/zepto8/commit/c83e3c448b254471d71885245e5ed9e14c4a9204)...

The `speaker` is not much more than a `mixer` with a locking mechanism. As long as `ctrl.Stream()`succeeds, `speaker` will keep playing your controller. No need to call `speaker.Play()` more than...

Same with `-h`, `-q`, `-v` and `-V`; it looks like the global options are copied to the commands…

While debugging Eris I have come across a few Valgrind warnings about uninitialised call info memory being serialised. This is harmless but does pollute error reporting when investigating issues, so...

I worked on this refactoring a long time ago because I wanted to keep track of my Lua patches more easily. I don’t know if it’s useful to you or...

Note that project Monitorian [seems to have the same problem](https://github.com/emoacht/Monitorian/issues/81) despite not using wpf-notifyicon and having their own wrapper around a WinForms icon instead (see their [notify icon code here](https://github.com/emoacht/Monitorian/blob/master/Source/ScreenFrame/NotifyIconContainer.cs)).

Hi! I believe this may have been fixed or at least mitigated with the audio engine rewrite (3c3abaf8df09620e345aad36f857c0ec9278bf6e). The audio buffer size and thus audio delay have been significantly reduced....

The Linux screensaver issue probably needs to be fixed in glfw, see https://github.com/glfw/glfw/issues/854.

I have some updates on this. The GopherJS port went pretty well, and I have now switched to WASM instead because GopherJS does not really support `unsafe.Pointer`. Here is a...