Skip to content
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

Add UI for pixel history for dual source output and blend src/dest #3010

Closed
wants to merge 10 commits into from

Conversation

w-pearson
Copy link
Contributor

Description

Split from #3003; depends on (and includes a copy of) #3009.

This PR modifies the pixel history UI to add additional columns for dual source blend and the blend source/destination components. Currently, those are not implemented for any API. It also adds a column for the previous color, for which data was already obtained but not visible in the UI. All of these columns are hidden by default.

It also fixes a few minor UI issues: there was a mistake in the right-click message on pixel history where the message was "Debug Pixel (<x>, <y>) primitive <event> at Event <primitive>", and the color columns in the pixel history view were always shown in the same color if the column was selected (now, the actual color is blended with the selection color to make things a bit clearer).

Currently, no backend sets this, and it is not displayed.
Currently, no backend sets them, and they are not displayed.
Before, if a row was selected, the color was completely replaced, which
makes the color preview column completely useless for that row.

This change also fixes some inconsistencies with how the selection hover
works on tree widgets; previously part of the row was not highlighted.
This is already implemented by all backends, but did not get displayed
beforehand. This column is not visible by default.
This has not yet been implemented by any backends, not is the column
visible by default.
They have not yet been implemented by any backends, not are the columns
visible by default.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants