Unnecessary usage of thread-local storage on Windows #94
Labels
C - waiting on author
Waiting for a response or another PR
D - hard
Likely harder than most tasks here
DS - windows
P - normal
Great to have
S - enhancement
Wouldn't this be the coolest?
Milestone
Currently, the win32 window callback relies on thread-local storage to stash data for the callback function. This isn't necessary - by using the win32 subclassing API, it is possible to pass a user-defined pointer into the window function with the
dwRefData
parameter in a subclass. By boxing up the callback data and freeing it when the window is destroyed, the use of thethread_local
macro can be avoided.The text was updated successfully, but these errors were encountered: