-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Support wp color management proto #9444
Conversation
thanks as always! tag me for review when this is ready. |
@vaxerski ready for review |
stellar work as always |
Truly Fast and active development |
@@ -12,6 +12,7 @@ | |||
#include "Timer.hpp" | |||
#include "math/Math.hpp" | |||
#include <optional> | |||
#include "protocols/types/ColorManagement.hpp" |
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.
this include is wrong, should be "../protocols/types/ColorManagement.hpp"
causes build failure for plugins: Duckonaut/split-monitor-workspaces#166
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.
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.
auto-import set me up %)
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.
Not really your fault though, preferably this would get picked up by the CI/CD and/or enforced through things like clang-tidy/clang-format/cppcheck
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.
auto-import set me up %)
what auto import are you using 😭 i didn't even know that was a thing for c++
Describe your PR, what does it fix/add?
Support wp color-management. #9443
Added
debug:full_cm_proto
to switch proto into debug mode (requires restart).In regular mode this implementation does almost nothing. It handles the minimum required subset of features.
In debug mode all features and values are marked as supported. Features related to fullscreen HDR will work the same as with xx-cm and frog-cm. Other features will only store and pass values and output some log messages.
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
Needs #9064 to be useful. Without it xx-cm and frog-cm should be used instead because those protos are less likely to break things for newer clients with correct wp-cm support.
Needs nix wp version bump.
Needs a proper way of handling images description ids to avoid duplication (not a priority, very unlikely conditions to be useful)
Is it ready for merging, or does it need work?
Ready.