I mean the program just terminates with exit code 139
I mean the program just terminates with exit code 139
Pwat
Pah
Pthat's a segfault error code
Pinformation available
PPmore information available
Pthese lines
Punknown.png4.34KB
P
Pyou're making the window current before you've even told GLFW to make and run it
Pmoreover, if we've implemented it correctly the window should already be current on the Render dispatcher
Pand if not, we need to implement that
VI tried that last night, even without calling MakeCurrent it doesn't work
Poh yeah
Punknown.png28.32KB
Pso the early MakeCurrent is a problem
Pbut not the problem
JThat's a typical issue when native code dereferences a null pointer
JAnd very common when you don't have a current GL context
J@Unknown user
Paha
Pwill give that a look
Pyou need a context current and GLFW current on the same thread in order to change properties
Pactually hang on
VIt's not a threading issue, using a single-threaded window does the same thing
V"When moving a context between threads, you must make it non-current on the old thread before making it current on the new one."
VSo it looks like that's why MakeContextCurrent doesn't work
Pthat's trash
Pugh
VEspecially since MakeContextCurrent forces a pipeline flush
Pyep
VMaybe we could set it for the proper thread in the constructor, and then remove MakeCurrent from the public API?
Vor just scratch that last part
Pto be honest
Pwe could get away with removing MakeCurrent
VI'd be fine with that
Pgiven that we have an Invoke method that people can use to access the render thread
VInvoke gives access to the glfw thread, not the render thread
Pwhaattt???
Pthat's not how it's meant to work!
P
VThat's how it's always worked
PGlfwWindow.Invoke?
VYep
Pthat's not what I had in mind :/
Pthe idea was people used that method so that they don't have to do anything stupid like try to move the context between threads