`IsContextControlDisabled` is important as well, the window system will keep trying to move your con
IsContextControlDisabled is important as well, the window system will keep trying to move your context back otherwise
Pone day i did intend to abstract all of this into a separate
GameLoop class that can be configured to automatically multithread, but sadly just a pipe dream now
HSpeaking of this one, i did this and do
context.MakeCurrent()
and
SwapBuffers()
Manually and it did increase the performance about 2x
context.MakeCurrent()
and
SwapBuffers()
Manually and it did increase the performance about 2x
Hbasically i skipped this part?
Phrmfffff SwapInterval has given me so much grief over these 3 years
Pi think it's actually the IsCurrent that'd be causing the perf hit
Pi mean do run it through dotTrace if you can, would be interesting to compare
HI see
Him still hit with the same errors as before
Hsame as when i run this repo
RGameLoop is too specific, I think something like ApplicationLoop would be better
Pdoesn't matter, it's not happening anyway
Rfair nuff
Pi may have missed a
ClearContextLoadis it inside or outside the render thread?
PRWhy do you guys make the context current automatically? Was there a specific reason?
Plike a lot of things in windowing it is designed for ease of use and to prevent confusion
Pimagine how a beginner would react if they couldn't issue any GL commands on their fresh window
Rfair enough...
HIt no longer crashes, but it doesn't do anything now
HHere's my window options
Pyou probably want to move SwapBuffers into your Render callback
Hthis is what i had
Pyou're probably double swapping somewhere
Hi dont think so?
Hhmmmm
Pheh
Pi have a feeling your render callback could be called on both threads
Hoh yea let me check
Hok yeah it's my code
HIt worked!
HThanks @Perksey
R@Perksey I think the input package for 2.16.0 is broken, I just updated to it and the window does not show up, but my application just sits there
PMake sure all of the package versions match, and if it’s still the same then I have no idea what’s changed
Pthere’s been some loader changes and some bindings regeneration but other than that nothings touched input between 2.15 and 2.16
Pbut also I’m not the person to ping anymore
Rsorry lol
Loh i never tested on windows lol
Lig i forgot to clear the context
Lyup
Llinux seems to be immune
Hdayum linux seems to have better windowing system
Hdoesnt freeze when resize and doesnt need to clear context
Lno
Lwindowing on linux is pain
VThe fact that there isn't really a single standard, and that one of them doesn't even support absolute positioning of windows or global shortcuts, definitely seems like a pain
RYes
RDoes Wayland really not support absolute positioning of windows
RI've heard Wayland is painful, but is it really that painful?
VYup 
It doesn't even have a concept of absolute positioning, the only way to move a window is to specify a relative offset, and all coordinates are relative to the window.
It doesn't even have a concept of absolute positioning, the only way to move a window is to specify a relative offset, and all coordinates are relative to the window.
