-
-
Notifications
You must be signed in to change notification settings - Fork 188
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.
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
feat(windows): allow setting window class name, closes #769 #770
Conversation
allow to customize it instead of current value hard coded "Window Class"
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution, could you also add a changefile in .changes directory?
Co-authored-by: Amr Bashir <[email protected]>
Co-authored-by: Amr Bashir <[email protected]>
allow to customize it instead of current value hard coded "Window Class"
Yes ! I added one (following the exemple of |
@wusyong should this API be ported to the v0.16 branch or wait until tauri v2? |
cherry picked into v0.16 in ae664f0 |
allow to customize the window class name instead of current value hard coded "Window Class"
Currently, on Windows, all windows created by Tao have the same class Window Class, it would be neet to allow for customization of the Windows' window class name. One use case: some windows custom hotkey managers leverage window class names to select windows...
Waiting for merge in upstream project winit (pass all 55 checks) : rust-windowing/winit#2978
(closing mirrored issue rust-windowing/winit#2977)
What kind of change does this PR introduce?
Does this PR introduce a breaking change?
Checklist