Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

add an order number for showing by call order instead of apply order? #26

Copy link
Copy link
@greggman

Description

@greggman
Issue body actions

I don't know if this would be useful or not but, the trace doesn't record what you did. It records the effect of what you did.

So,

const commandEncoder = device.createCommandEncoder();
const passEncoder = commandEncoder.beginRenderPass(renderPassDescriptor);
passEncoder.setPipeline(pipeline);
passEncoder.draw(1)
device.queue.writeBuffer()
passEncoder.end();
device.queue.submit([commandEncoder.finish()]);

Will show up in the trace as

createEncoder
writeBuffer
submit
   pass
      setPipeline
      draw

If each command recorded an order id then we could optionally display the commands in call order. Not sure how useful that is. I'm just worried that devs will want to see what they did, not just results of what they did.

Like the mapAsync being translated in bufferUpdateData, I think the user would like to see mapAsyc, getMappedRange, unmap? or not?

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.