umläute

thanks. no idea how i missed this. unfortunately the fork is one of those "contributor forks" with no issues, PRs and whatnot. i would still prefer to move the maintenance...

just to chime in with my new SuperMicro X12DPi-N6 board: ``` root@localhost:~# lspci | egrep '(MEI|HECI)' 00:16.0 Communication controller: Intel Corporation C620 Series Chipset Family MEI Controller #1 (rev 0a)...

hmm. `[render_trigger]` really behaves the same as `[trigger]` (with the outlets swapped). it was necessary at a time (more than 2 decades ago), when `[gemhead]` would not emit a message...

from a conceptual model, i think the *current* behaviour is the only sane option. (we do need to cleanup the render-state at some point, and once a subtree has done...

sigh. it seems to work on Linux (Debian, Linux-6.7.9, Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics])

@jamshark70 i don't really know, but she could try changing the windowing backend, by changing the `gemdefaultwindow.pd` abstraction in the Gem/-folder and replacing the `[gemmacoswindow]` (or whatever is there) to...

could you try with `[gemglfw3window]`? (you need to have `glfw` installed before running `./configure`)

> the window also can't be closed by clicking the close button but that's not too big of a deal. that's actually a feature. the `[gemwin]` object (well, the `[gemglfw3window]`...

the crash is weirder (but should probably be discussed in a separate ticket)

i hope that you only get the error message once.