Fix incorrectly named methods in ResourceFormat

* We try to maintain at least an internally consistent naming scheme for the
  python/public interface, even if it doesn't match python naming schemes.
This commit is contained in:
baldurk
2019-01-03 12:22:29 +00:00
parent c154a16442
commit 2237c241ff
21 changed files with 173 additions and 173 deletions
+3 -3
View File
@@ -840,7 +840,7 @@ void TextureViewer::UI_UpdateStatusText()
float g = qBound(0.0f, m_CurHoverValue.floatValue[1], 1.0f);
float b = qBound(0.0f, m_CurHoverValue.floatValue[2], 1.0f);
if(tex.format.srgbCorrected() || (tex.creationFlags & TextureCategory::SwapBuffer))
if(tex.format.SRGBCorrected() || (tex.creationFlags & TextureCategory::SwapBuffer))
{
r = powf(r, 1.0f / 2.2f);
g = powf(g, 1.0f / 2.2f);
@@ -1411,7 +1411,7 @@ void TextureViewer::UI_UpdateChannels()
}
else
{
if(tex != NULL && !tex->format.srgbCorrected())
if(tex != NULL && !tex->format.SRGBCorrected())
ENABLE(ui->gammaDisplay);
else
DISABLE(ui->gammaDisplay);
@@ -1420,7 +1420,7 @@ void TextureViewer::UI_UpdateChannels()
!ui->gammaDisplay->isEnabled() || ui->gammaDisplay->isChecked();
}
if(tex != NULL && tex->format.srgbCorrected())
if(tex != NULL && tex->format.SRGBCorrected())
m_TexDisplay.linearDisplayAsGamma = false;
bool dsv = false;