Stéphane Gagnon

Hi @jofemodo We are waiting for about 8 years for any news from the author, good luck. But your project is interesting. I think depending on the license, you can...

Hi, The author has abandonned this version since 2015 and your PR will be never processed Those changes are all done in the new mididings community fork [https://github.com/mididings/mididings](https://github.com/mididings/mididings) Please, considere...

At last! This is very good news and I had been hoping for this for years, this software should not die under any circumstances. I want to contribute as best...

I am actually using boost 1.78.0 on my Raspbian OS; I will use mididings with Python 3.10 for the moment, it's not a problem for me, but I will rebuild...

FYI mididings works fine with Boost 1.81 and Python 3.11 and the pyliblo fixed for 3.11 (thanks again) $ ldd ./build/lib.linux-x86_64-cpython-311/_mididings.cpython-311-x86_64-linux-gnu.so **libboost_python311.so.1.81.0 => /usr/lib/x86_64-linux-gnu/libboost_python311.so.1.81.0 (0x00007fa035a3d000) libboost_thread.so.1.81.0 => /usr/lib/libboost_thread.so.1.81.0 (0x00007fa035825000)** Boost...

**References:** - The event API project: https://github.com/pyeve/events - WIP : https://github.com/stefets/mpyg321/tree/events

> It looks interesting, I'll give it a look. What about using decorators on the event callback instead of explicitly adding it? Hi! if a decorator can help simplify the...

Hi! If your modification can replace Events that's even better, it's one less dependency but I want to avoid reinventing the wheel and the code that Events allows must be...

> PS: @stefets now I know why I wanted to keep the frame output :p ... Yes! :) It wasn't long before a use case appeared!

@ehanuise have you tried this editor ? It state : It's in a very early stage of development and has not been thoroughly tested. Use at your own risk. I...