OSYSTEM: Mention that our OSystem graphics API is not thread safe.
Based on f621f6a505
and the fact that our OpenGL
based backends do not (and sometimes cannot easily) implement it in a thread
safe manner.
This commit is contained in:
parent
df3bc62a3a
commit
bcd07d35bb
1 changed files with 5 additions and 0 deletions
|
@ -403,6 +403,11 @@ public:
|
||||||
* factor 2x, too, just like the game graphics. But if it has a
|
* factor 2x, too, just like the game graphics. But if it has a
|
||||||
* cursorTargetScale of 2, then it shouldn't be scaled again by
|
* cursorTargetScale of 2, then it shouldn't be scaled again by
|
||||||
* the game graphics scaler.
|
* the game graphics scaler.
|
||||||
|
*
|
||||||
|
* On a note for OSystem users here. We do not require our graphics
|
||||||
|
* to be thread safe and in fact most/all backends using OpenGL are
|
||||||
|
* not. So do *not* try to call any of these functions from a timer
|
||||||
|
* and/or audio callback (like readBuffer of AudioStreams).
|
||||||
*/
|
*/
|
||||||
//@{
|
//@{
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue