Rename 'draw' or 'drawcall' to action

* There's not a good accepted terminology for this kind of event, and for
  historical reasons 'drawcall' has been the accepted term, even though
  that can be quite confusing when a dispatch or a copy is a 'drawcall'.
* This is particularly highlighted by the event browser filters where
  $draw() includes draws and dispatches, but $dispatch() only includes
  dispatches, it's hard to intuitively understand why $draw() matches all
  of these calls.
* As a result we've defined the term 'action' to cover these types of
  events in the same way that we defined 'event' in the first place to
  mean a single atomic API call.
This commit is contained in:
baldurk
2021-06-23 18:14:18 +01:00
parent e7785bd99e
commit 7149302680
283 changed files with 5374 additions and 5320 deletions
+4 -4
View File
@@ -188,7 +188,7 @@ void TipsDialog::initialize()
"to view the history of in the texture viewer, and click the 'history' button underneath "
"the zoomed-in pixel context.\n\nEach event will show up red or green depending on "
"whether it affected or didn't affect the pixel. By expanding the event, you can see the "
"possibly several primitives within the draw that overdrew the pixel.\n")));
"possibly several primitives within the action that overdrew the pixel.\n")));
// Tip 18
m_tips.push_back(
@@ -209,7 +209,7 @@ void TipsDialog::initialize()
// Tip 20
m_tips.push_back(
Tip(tr("Gathering of per-event callstacks"),
tr("RenderDoc is able to gather callstacks either per-drawcall or per-API event. You can "
tr("RenderDoc is able to gather callstacks either per-action or per-API event. You can "
"do this by enabling the option before launching an application capture.\n\nWhen "
"loading the log, initially the callstacks will not be available until symbols are "
"resolved. Go to tools -> resolve symbols to load up the pdbs matching the modules "
@@ -219,7 +219,7 @@ void TipsDialog::initialize()
m_tips.push_back(Tip(
tr("Texture debugging overlays"),
tr("In the texture viewer, you can select from several helpful debugging overlays over the "
"current view. This can show wireframe or solid coloour overlays of the current drawcall, "
"current view. This can show wireframe or solid coloour overlays of the current action, "
"as well as showing depth pass/fail or even representing quad overdraw as a heatmap.\n")));
// Tip 22
@@ -268,7 +268,7 @@ void TipsDialog::initialize()
m_tips.push_back(
Tip(tr("Event browser keyboard shortcuts"),
tr("In the event browser Ctrl-F opens up the find bar, to locate an event by its name. "
"Ctrl-G opens the jump-to-event to jump to the closest drawcall to a numbered event. "
"Ctrl-G opens the jump-to-event to jump to the closest action to a numbered event. "
"Ctrl-B will toggle a bookmark at the current event.\n")));
// Tip 28