Skip to content

Named issues about FormatB8G8R8A8Unorm #728

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

Closed
lindexi opened this issue Dec 22, 2021 · 3 comments
Closed

Named issues about FormatB8G8R8A8Unorm #728

lindexi opened this issue Dec 22, 2021 · 3 comments

Comments

@lindexi
Copy link
Member

lindexi commented Dec 22, 2021

I think it should be UNorm not Unorm.

The UNorm means two words: unsigned-normalized.

@Perksey
Copy link
Member

Perksey commented Dec 22, 2021

Closing as “won’t fix” (and duplicate of #458 same underlying cause)

I agree, but

  • these are generated bindings so we will have to special case these in the generator. Not a problem, but
  • this would be a breaking change, which we are not prepared to do at this time.
  • at least we’re consistently wrong throughout the library.

We will one day try and fix this as part of #458, but in the short/mid-term this will not be fixed.

@Perksey Perksey closed this as completed Dec 22, 2021
@Perksey
Copy link
Member

Perksey commented Dec 22, 2021

#427 not #425 🙈

@lindexi
Copy link
Member Author

lindexi commented Dec 22, 2021

Thank you @Perksey

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

No branches or pull requests

2 participants