lee/renderdoc
1
0
Fork 0
mirror of https://github.com/baldurk/renderdoc.git synced 2026-08-29 01:46:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

Rename previous/next to previousAction/nextAction in ActionDescription

Browse Source 
* swig internally creates 'next' member which we normally want to avoid, so
  prevent shadowing here by using a distinct name.
This commit is contained in:
baldurk
2026-08-13 17:46:47 +01:00
parent 40945e6e8a
commit 950568fb8f
75 changed files with 226 additions and 226 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/python_api/examples/renderdoc/iter_actions.rst
+1 -1
View File
@@ -7,7 +7,7 @@ The actions returned from :py:meth:`~renderdoc.ReplayController.GetRootActions`
The first way illustrated in this sample is to walk the tree using :py:attr:`~renderdoc.ActionDescription.children`, which contains the list of child actions at any point in the tree. There is also :py:attr:`~renderdoc.ActionDescription.parent` which points to the parent action.
The second is to use :py:attr:`~renderdoc.ActionDescription.previous` and :py:attr:`~renderdoc.ActionDescription.next`, which point to the previous and next action respectively in a linear fashion, regardless of nesting depth.
The second is to use :py:attr:`~renderdoc.ActionDescription.previousAction` and :py:attr:`~renderdoc.ActionDescription.nextAction`, which point to the previous and next action respectively in a linear fashion, regardless of nesting depth.
In the example we use this iteration to determine the number of passes, using the action flags to denote the start of each pass by a starting clear call.