Skip to content

Unnecessary usage of thread-local storage on Windows #94

@Osspial

Description

@Osspial

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 the thread_local macro can be avoided.

Metadata

Metadata

Assignees

No one assigned

    Labels

    C - waiting on authorWaiting for a response or another PRD - hardLikely harder than most tasks hereDS - win32Affects the Win32/Windows backendP - normalGreat to haveS - enhancementWouldn't this be the coolest?

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions