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 a warning for FRenderableManager #8210

Merged
merged 4 commits into from
Oct 20, 2024
Merged

Add a warning for FRenderableManager #8210

merged 4 commits into from
Oct 20, 2024

Conversation

z3moon
Copy link
Contributor

@z3moon z3moon commented Oct 17, 2024

In some cases, users set materials first without providing render primitives, which has incurred the attribute mismatching warning. This isn't helpful because users don't know what action they should take to remove the warning.

Emit the warning only when the primitive handle is initialized so the AttributeBitset is properly populated.

BUGS=[372755205]

In some cases, users set materials first without providing render
primitives, which has incurred the attribute mismatching warning. This
isn't helpful because users don't know what action they should take to
remove the warning.

Add a more specific warning for this case with which users know the
direct cause and what to do to remove the warning.

BUGS=[372755205]
@z3moon z3moon added the internal Issue/PR does not affect clients label Oct 17, 2024
Copy link
Collaborator

@pixelflinger pixelflinger left a comment

Choose a reason for hiding this comment

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

Okay I understand the problem. I don't think we should have a warning when the handle is undefined -- that's an okay situation.

Instead, I think we should only emit the original "attribute mismatch" warning when the handle is defined. Otherwise we simply can't tell, so let's not print anything.

@z3moon
Copy link
Contributor Author

z3moon commented Oct 18, 2024

That also works. Let me update the change.

@z3moon z3moon enabled auto-merge (squash) October 20, 2024 15:00
@z3moon z3moon merged commit 2456299 into main Oct 20, 2024
9 checks passed
@z3moon z3moon deleted the zm/add-warning branch October 20, 2024 15:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal Issue/PR does not affect clients
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants