File: resource_inspector.rst

package info (click to toggle)
renderdoc 1.24%2Bdfsg-1%2Bdeb12u1
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 105,156 kB
  • sloc: cpp: 759,405; ansic: 309,460; python: 26,606; xml: 22,599; java: 11,365; cs: 7,181; makefile: 6,707; yacc: 5,682; ruby: 4,648; perl: 3,461; sh: 2,354; php: 2,119; lisp: 1,835; javascript: 1,524; tcl: 1,068; ml: 747
file content (46 lines) | stat: -rw-r--r-- 2,247 bytes parent folder | download | duplicates (4)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
Resource Inspector
==================

The resource inspector window allows you to see a full list of all API objects included in the frame capture. You can see the relationships between objects - such as parent/child links - as well as the full creation details of any object.

.. |link| image:: ../imgs/icons/link.png

Links to the resource inspector exist throughout the UI indicated by a **bold resource name** and the |link| icon.

.. figure:: ../imgs/Screenshots/resource_inspector.png

	Resource Inspector: Examining the details of a resource in a capture.

Related Resources
-----------------

For the selected resource, if there are any parent resources which this resource depends on, they will be listed under related resources. Similarly in the parent resource, any children are listed here too. This lets you easily click from one to the other.

An example of a parent-child relationship is a 'view' type object that is created in reference to a concrete 'image' or 'texture' type object.

Usage in Frame
--------------

Some resources such as textures and buffers have information available about where and how they're used in the frame.

In this list, each entry lists an EID range and a type of usage.

Resource Initialisation Parameters
----------------------------------

Before any API object is used in the frame, it must be initialised and set up exactly as it was in the captured application.

The function calls used to initialise the object are listed here, which will normally contain at least one creation function.

Renaming resources
------------------

To rename resources, click on the :guilabel:`Rename Resource` button next to the name, and it will open an editing textbox to let you change the name. When you've set the name, press :kbd:`Enter` or click :guilabel:`Rename Resource` again. To cancel a rename, press :kbd:`Escape` or click :guilabel:`Reset name` to restore the name to its original value.

This name will be used consistently throughout the UI anywhere the resource is referenced, and will update whenever you rename it again.

.. figure:: ../imgs/Screenshots/resource_rename.png

	Resource Inspector: Renaming a resource in a capture.

For more information, see :doc:`../how/how_annotate_capture`.