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.

Sign up for GitHub

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

Jump to bottom

Remove the Destroyed state from Storage #4970

Merged
merged 3 commits into from
Jan 11, 2024
Merged

Remove the Destroyed state from Storage #4970

merged 3 commits into from
Jan 11, 2024

Commits on Jan 11, 2024

  1. Remove the Destroyed state from Storage 

    It used to be how we handled destroying buffers and textures but we moved to different approach.
    @nical
    nical committed Jan 11, 2024
    Configuration menu
    Copy the full SHA
    8524bed View commit details
    Browse the repository at this point in the history

  2. Explicit check for destroyed textures/buffers in a few entry points 

    This used to be checked automatically when getting the resource from the registry, but has to be done manually now that we track we track the destroyed state in the resources.
    @nical
    nical committed Jan 11, 2024
    Configuration menu
    Copy the full SHA
    5e92751 View commit details
    Browse the repository at this point in the history

  3. Merge branch 'trunk' into mark-destroyed

    @nical
    nical authored Jan 11, 2024
    Configuration menu
    Copy the full SHA
    7d2403a View commit details
    Browse the repository at this point in the history