Skip to content

fix(windows): give wmSetTitle its own message number #17

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
xiaoyumuxi merged 1 commit into from
Nov 14, 2026
Merged

fix(windows): give wmSetTitle its own message number #17

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions internal/platform/windows/title_windows.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,10 @@ import (

// wmSetTitle asks the window thread to apply the title SetTitle stored.
// SetWindowTextW from another thread would send WM_SETTEXT and wait for the
// window thread, so the change is posted instead.
const wmSetTitle = 0x8052
// window thread, so the change is posted instead. Its number is the next free
// one after wmSetSize (0x8052): the window procedure switches on every private
// message, and two of them with one number do not compile.
const wmSetTitle = 0x8053

var setWindowText = user.NewProc("SetWindowTextW")

Expand Down
Loading