diff options
author | Nat Goodspeed <nat@lindenlab.com> | 2019-10-22 16:36:16 -0400 |
---|---|---|
committer | Nat Goodspeed <nat@lindenlab.com> | 2020-03-25 19:00:10 -0400 |
commit | 253e360062a74cbaf87c7f9dc30ef26bca1697eb (patch) | |
tree | 85eff2023471201e29983e9591826a289c6440a9 | |
parent | aea1e469820d276d0bc077fb8b3a77a5e6a35faf (diff) |
DRTVWR-476: Mention LLApp::stepFrame() in LLAppViewer::idle()
which performs "by hand" the same sequence of calls found in stepFrame().
Why not simply call stepFrame()? Hysterical reasons?
-rw-r--r-- | indra/newview/llappviewer.cpp | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/indra/newview/llappviewer.cpp b/indra/newview/llappviewer.cpp index db2db43ee1..1bba17dc29 100644 --- a/indra/newview/llappviewer.cpp +++ b/indra/newview/llappviewer.cpp @@ -4610,6 +4610,9 @@ void LLAppViewer::idle() LLFrameTimer::updateFrameTime(); LLFrameTimer::updateFrameCount(); LLEventTimer::updateClass(); + // LLApp::stepFrame() performs the above three calls plus mRunner.run(). + // Not sure why we don't call stepFrame() here, except that LLRunner seems + // completely redundant with LLEventTimer. LLNotificationsUI::LLToast::updateClass(); LLSmoothInterpolation::updateInterpolants(); LLMortician::updateClass(); |