PCSX2 Documentation/Passing Settings Between Threads: Difference between revisions
PCSX2 Documentation/Passing Settings Between Threads (view source)
Revision as of 17:25, 19 July 2015
, 19 July 2015no edit summary
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
In PCSX2, the User Interface and the Virtual Machine both incorporate multithreaded design. Because of this, the UI and VM threads cannot modify each others' data and configurations directly, unless they first assure that the other thread is in a completely suspended state. | In PCSX2, the User Interface and the Virtual Machine both incorporate multithreaded design. Because of this, the UI and VM threads cannot modify each others' data and configurations directly, unless they first assure that the other thread is in a completely suspended state. | ||
Line 17: | Line 16: | ||
In order to have settings changes saved you must modify the contents of the g_Conf structure, and modification of that should only be done from the context of the UI thread. If the VM thread wants to make permanent modifications to the user's configuration (and there's not a lot of good reason for that), then it should be done using message postings. | In order to have settings changes saved you must modify the contents of the g_Conf structure, and modification of that should only be done from the context of the UI thread. If the VM thread wants to make permanent modifications to the user's configuration (and there's not a lot of good reason for that), then it should be done using message postings. | ||
{{PCSX2 | |||
{{PCSX2 Documentation Navbox}} |