jimy byerley

Currently I am hesitating between 2 designs for the end-user API of `Kinematic` class ## intrinsics The `Kinematic` class is intrisicly a solver whose main methods are - `parts(state) ->...

An other hesitation I have is: should the joint variables change to be a `numpy.void` type, with a structured dtype instead of nested tuples like now ? a draft of...

Lets continue with nested tuples for now and solid matrix poses as output. for joint space as output, the user will still be able to use `.solve()` and `.freedom()` For...

news about this: kinematic chains are very fast to solve and very stable  kinematic with many loops are working fine as well, but much more computational and not always...

Any news on this ? I get the same error on debian 12 using wayland, and likewise no problem using Xorg (of course xorg tends to be deprecated so I...

The problem is: I'm not trying to instantiate a standalone context, I am trying to use a `QOpenGLWidget` so I do not control whether I'm using openGL or openGLES using...

Hum ... but `moderngl.create_context()` was what I did before, and I still get the issue decribed in the initial post of the thread even with moderngl 5.10. I just tries...

I will try it Here is a minimal example to reproduce the issue by the way ```python from PyQt5.QtWidgets import QOpenGLWidget, QApplication from PyQt5.QtGui import QSurfaceFormat from PyQt5.QtCore import Qt...

just tested it: version 6.0 from the main branch (commit e175d069a13fd7bbc38e34fb8cfce447d91e0ff5) works on wayland ! I have errors on some buffer creation I did not had before, meaning moderngl 6...

Out of interested curiosity: when do you plan to release moderngl 6.0 ?