From: Jordan Justen Date: Wed, 25 Aug 2021 16:31:33 -0700 Subject: renderdoc: Fix misspelling: preceeded => preceded Signed-off-by: Jordan Justen --- docs/python_api/examples/basics.rst | 2 +- qrenderdoc/Code/QRDUtils.cpp | 8 ++++---- renderdoc/driver/shaders/dxbc/dxbc_bytecode_vendorext.cpp | 2 +- renderdoc/driver/shaders/dxbc/official/cvinfo.h | 2 +- 4 files changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/python_api/examples/basics.rst b/docs/python_api/examples/basics.rst index ea09cec..5d6dbd6 100644 --- a/docs/python_api/examples/basics.rst +++ b/docs/python_api/examples/basics.rst @@ -17,7 +17,7 @@ Some methods like the two above return information which is global and does not During RenderDoc's replay, you can imagine a cursor that moves back and forth between the start and end of the frame. All requests for information that varies - such as texture and buffer contents, pipeline state, and other information will be relative to the current event. -Every function call within a frame is assigned an ascending ``eventId``, from ``1`` up to as many events as are in the frame. Within the action list returned by :py:meth:`~renderdoc.ReplayController.GetRootActions`, each action contains a list of events in :py:attr:`~renderdoc.ActionDescription.events`. These contain all of the ``eventId`` that immediately preceeded the action. The details of the function call can be found by using :py:attr:`~renderdoc.APIEvent.chunkIndex` as an index into the structured data returned from :py:meth:`~renderdoc.GetStructuredFile`. The structured data contains the function name and the complete set of parameters passed to it, with their values. +Every function call within a frame is assigned an ascending ``eventId``, from ``1`` up to as many events as are in the frame. Within the action list returned by :py:meth:`~renderdoc.ReplayController.GetRootActions`, each action contains a list of events in :py:attr:`~renderdoc.ActionDescription.events`. These contain all of the ``eventId`` that immediately preceded the action. The details of the function call can be found by using :py:attr:`~renderdoc.APIEvent.chunkIndex` as an index into the structured data returned from :py:meth:`~renderdoc.GetStructuredFile`. The structured data contains the function name and the complete set of parameters passed to it, with their values. To change the current active event and move the cursor, you can call :py:meth:`~renderdoc.ReplayController.SetFrameEvent`. This will move the replay to represent the current state immediately after the given event has executed. diff --git a/qrenderdoc/Code/QRDUtils.cpp b/qrenderdoc/Code/QRDUtils.cpp index 3ff5d82..0f1588a 100644 --- a/qrenderdoc/Code/QRDUtils.cpp +++ b/qrenderdoc/Code/QRDUtils.cpp @@ -536,7 +536,7 @@ bool HandleURLFragment(RichResourceTextPtr linkedText, QString text, bool parseU int end = urlMatch.capturedEnd(); - // push any text that preceeded the url. + // push any text that preceded the url. if(urlMatch.capturedStart(0) > 0) linkedText->fragments.push_back(text.left(urlMatch.capturedStart(0))); @@ -641,7 +641,7 @@ void RichResourceTextInitialise(QVariant &var, ICaptureContext *ctx, bool parseU qulonglong idnum = match.captured(2).toULongLong(); memcpy(&id, &idnum, sizeof(id)); - // push any text that preceeded the ResourceId. + // push any text that preceded the ResourceId. if(match.capturedStart(1) > 0) HandleURLFragment(linkedText, text.left(match.capturedStart(1)), parseURLs); @@ -655,7 +655,7 @@ void RichResourceTextInitialise(QVariant &var, ICaptureContext *ctx, bool parseU link.eid = match.captured(6).toUInt(); link.numMessages = match.captured(7).toUInt(); - // push any text that preceeded the msgs link. + // push any text that preceded the msgs link. if(match.capturedStart(5) > 0) HandleURLFragment(linkedText, text.left(match.capturedStart(5)), parseURLs); @@ -685,7 +685,7 @@ void RichResourceTextInitialise(QVariant &var, ICaptureContext *ctx, bool parseU continue; } - // push any text that preceeded the EID. + // push any text that preceded the EID. if(match.capturedStart(3) > 0) HandleURLFragment(linkedText, text.left(match.capturedStart(3)), parseURLs); diff --git a/renderdoc/driver/shaders/dxbc/dxbc_bytecode_vendorext.cpp b/renderdoc/driver/shaders/dxbc/dxbc_bytecode_vendorext.cpp index bb75f23..919947a 100644 --- a/renderdoc/driver/shaders/dxbc/dxbc_bytecode_vendorext.cpp +++ b/renderdoc/driver/shaders/dxbc/dxbc_bytecode_vendorext.cpp @@ -305,7 +305,7 @@ void Program::PostprocessVendorExtensions() // happens is that when we see opode get written if it's NV_EXTN_OP_FP16_ATOMIC then we jump // straight to UAVInstructionBody and re-use the UAV instruction header from last time. We // know this MUST be a continuation because otherwise NV_EXTN_OP_FP16_ATOMIC is always - // preceeded by a UAV instruction header (via markUAV). + // preceded by a UAV instruction header (via markUAV). InstructionHeader, InstructionBody, // we move from Instruction1Out to this state when markUAV is written. The next UAV write is diff --git a/renderdoc/driver/shaders/dxbc/official/cvinfo.h b/renderdoc/driver/shaders/dxbc/official/cvinfo.h index 92b6a43..f67a494 100644 --- a/renderdoc/driver/shaders/dxbc/official/cvinfo.h +++ b/renderdoc/driver/shaders/dxbc/official/cvinfo.h @@ -2263,7 +2263,7 @@ typedef struct lfModifierEx { * size of the following variable length data. When the numeric * data is a single byte less than 0x8000, then the data is output * directly. If the data is more the 0x8000 or is a negative value, - * then the data is preceeded by the proper index. + * then the data is preceded by the proper index. */