I'm back from my paragliding training, and am so, so thankful for my giant 4K monitor again. I hate programming via a tiny laptop screen! It feels like making a ship in a bottle.

My goal right now is to get the MacOS support to a good stopping point before going back to working on the time-dilation voice instancing (which is a MUCH more fun project). So far I have about 60% of the unit tests passing on MacOS. Some percentage of those I'm going to leave broken -- for the time being I am not planning to work on the OpenCL support for MacOS, since that can be a future subproject, or I may just never do it and go straight to Metal first.

A lot of what I've been running into with the tests is just annoying stuff having to do with the way MacOS GUI stuff works compared to Windows. In a way, the problems there are largely my fault, because the hacky way I got unit tests working on Windows was never all that great. So today I was forced to rethink how GUI unit tests work and came up with a much more general solution that works on both OSes without a lot of hassle.

Once I get all the unit tests I care about passing, I will clean up a lot of the little MacOS hacks, and then I'd like to set up some kind of automatic build system so that while I'm developing on Windows, each git commit is automatically pulled and tested on MacOS so I know I'm not breaking anything.