Windows support #4
Labels
No labels
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: rosethorn/libxosd-xft#4
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Moving from rosethorn/XOSD-xft_affirmations#1. Add Windows API stuff so this can be compiled and used on Windows too.
@ryonia If you want to look into this more:
https://stackoverflow.com/questions/4062606/how-can-i-produce-an-osd-in-windows
https://stackoverflow.com/questions/29091028/windows-api-write-to-screen-as-on-screen-display
https://stackoverflow.com/questions/23300525/nativewindow-equivalent
https://learn.microsoft.com/en-us/windows/win32/learnwin32/creating-a-window
I don't know if it would be best to write it in a separate library, or either write it in separate files as part of this repository or in the same files with precompiler macros, but ideally I'd prefer it to be a single cross-platform library.
I'd personally prefer the single library too. There doesn't seem to be much in the way of this for Windows, and what little I can find out there just has people writing their own code to set up the on screen display, so why not have it all collected in one place?
Maybe we could start calling it XPOSD for Cross Platform On-Screen Display. :P
I don't really know how best to structure it, though. You'd all probably have a better idea.