Fix wxThread::SetPriority() documentation

The documentation's notes about MSW limitations about setting priority
before creating the thread do not appear to be true (anymore). Thread
priority is already set by Create() if SetPriority() was called earlier.
Setting it immediately just failed, because the thread did not exist
yet, but this was fixed by the previous commit.
This commit is contained in:
Lauri Nurmi
2019-12-20 11:01:07 +02:00
committed by Vadim Zeitlin
parent 2c4f42608b
commit 84f7e925e5
2 changed files with 0 additions and 8 deletions

View File

@@ -1267,11 +1267,6 @@ public:
- @c wxPRIORITY_DEFAULT: 50
- @c wxPRIORITY_MAX: 100
Notice that in the MSW implementation the thread priority can currently
be only set after creating the thread with CreateThread(). But under
all platforms this method can be called either before launching the
thread using Run() or after doing it.
Please note that currently this function is not implemented when using
the default (@c SCHED_OTHER) scheduling policy under POSIX systems.
*/