Skip to content

Qt: Disable UI of settings forced via gamedb, part two#3561

Merged
stenzek merged 1 commit intostenzek:masterfrom
Pesa:force2
Sep 9, 2025
Merged

Qt: Disable UI of settings forced via gamedb, part two#3561
stenzek merged 1 commit intostenzek:masterfrom
Pesa:force2

Conversation

@Pesa
Copy link
Contributor

@Pesa Pesa commented Sep 9, 2025

Sorry, missed these in #3558.

gpu_pgxp_preserve_proj_fp is treated specially because it can be set to true or false in the db.

Missed these in the previous commit.
m_dialog->hasGameTrait(GameDatabase::Trait::ForcePGXPVertexCache));
SettingWidgetBinder::SetForceEnabled(m_ui.pgxpDisableOn2DPolygons,
m_dialog->hasGameTrait(GameDatabase::Trait::DisablePGXPOn2DPolygons));
if (auto dbentry = m_dialog->getDatabaseEntry(); dbentry && dbentry->gpu_pgxp_preserve_proj_fp.has_value())
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like this should be in a helper functions, since there will be other traits that behave the same way such as those above it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

isn't gpu_pgxp_preserve_proj_fp the only one with an explicit true/false value in the db?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was more thinking from the perspective of "results in a forced value", e.g. force software renderer. But eh, I guess the availability kinda handles it.

@stenzek stenzek merged commit aee897e into stenzek:master Sep 9, 2025
11 checks passed
@Pesa Pesa deleted the force2 branch September 9, 2025 15:43
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