From 7a1c8d39f8ceda635519a93bb0299b3f2376d7c9 Mon Sep 17 00:00:00 2001 From: taler21 Date: Mon, 27 Nov 2023 18:38:06 +0100 Subject: [PATCH] Fix references to wxEventLoop::YieldFor() in the documentation It was incorrectly called wxAppConsole::YieldFor() but the function was moved from wxAppConsole to wxEventLoopBase back in dde19c2180 (second part of #10320: move wxApp event handling functions to wxEventLoopBase (in particular move Yield() functions); add backward compatible redirections to wxApp; update docs; remove global lists wxPendingEvents and wxPendingEventsLocker, 2009-02-15). Closes #24095. --- docs/doxygen/overviews/thread.h | 2 +- interface/wx/app.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/doxygen/overviews/thread.h b/docs/doxygen/overviews/thread.h index ba78317804..e16bb56b2f 100644 --- a/docs/doxygen/overviews/thread.h +++ b/docs/doxygen/overviews/thread.h @@ -36,7 +36,7 @@ To implement non-blocking operations @e without using multiple threads you have two possible implementation choices: - use wxIdleEvent (e.g. to perform a long calculation while updating a progress dialog) -- do everything at once but call wxWindow::Update() or wxApp::YieldFor(wxEVT_CATEGORY_UI) +- do everything at once but call wxWindow::Update() or wxEventLoopBase::YieldFor(wxEVT_CATEGORY_UI) periodically to update the screen. However, it is generally much better to run time-consuming tasks in worker threads instead diff --git a/interface/wx/app.h b/interface/wx/app.h index b27e504fcb..d5f30778b7 100644 --- a/interface/wx/app.h +++ b/interface/wx/app.h @@ -936,7 +936,7 @@ public: Works like SafeYield() with @e onlyIfNeeded == @true except that it allows the caller to specify a mask of events to be processed. - See wxAppConsole::YieldFor for more info. + See wxEventLoopBase::YieldFor() for more info. */ virtual bool SafeYieldFor(wxWindow *win, long eventsToProcess);