some time ago I tried to use GLWidget. It is a C# only control for GTK# that manages an opengl view and uses OpenTK internally. Because it didn't work properly I started to fix it on all 3 supported platforms (Windows, X11, OSX).
During development stumbled over some issues in OpenTK that I can work around but I think they should be resolved in OpenTK. The issues are caused by the specific situation of using OpenTK in an GTK control.
1. A GTK control doesn't always use the same window during it's lifetime. When a control is realized its window gets created. When the window gets unrealized its window gets destroyed. This is used in docking libraries where windows get reparented. So it is necessary to use the OpenGL context of the control and bind it to another window.
This is currently not easily possible on all platforms.
The Graphics context only calls SetPixelFormat for the window it is created with. So when additional windows are created they don't get set up correctly.
When calling MakeCurrent the AglGraphicsContext doesn't care about the window info at all. It just makes the opengl context current. The drawable stays unchanged.
2. OpenTK has the habit of calling XInitThreads in its initialization under X11. This call is used to make multithreaded OpenGL work. The problem with this call is that it has to be the first function in Xlib that is called. Otherwise the behavior is undefined. The problem is that in my control where I use OpenTK it gets initialized at some point I have no control of. When my control is created it is quite certain that there are already some X11 windows created. So when I initialize OpenTK in the ctor the call to XInitThreads causes dubious crashes at different places.
I would have to tell every user of my control to call some static function or initialize OpenTK themselves before they do any X11 calls. This is problematic as is is very unusual for a GTK control to require such things and people tend not to read documentations.
May be I'm overlooking something but I really think these issues are relatively easy to fix and I offer to do the coding as I currently have access to all platforms. Could some developer at least drop a single line if this is appreciated? Even tell me if don't care about these issues at all because you think the use case I have is too obscure. This would be totally OK as OpenTK is open source and I can just fork it if I want.