PCSX2 Documentation/Thread Synchronization: Difference between revisions
Jump to navigation
Jump to search
PCSX2 Documentation/Thread Synchronization (view source)
Revision as of 17:33, 19 July 2015
, 19 July 2015no edit summary
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 6: | Line 6: | ||
* Load the image one scanline at a time, and then after each scanline manually check for keyboard, mouse, or other input, and refresh the screen. | * Load the image one scanline at a time, and then after each scanline manually check for keyboard, mouse, or other input, and refresh the screen. | ||
* Load the image using a thread, and let the usual "global" windows message handler dispatch keyboard, mouse, and refresh messages as usual. | * Load the image using a thread, and let the usual "global" windows message handler dispatch keyboard, mouse, and refresh messages as usual. | ||
| Line 18: | Line 17: | ||
#Use a "friendly" blocking mechanism that periodically polls the user input and updates display. This is no better than cooperative single-thread designs though, as it has slow response times and doesn't scale well to multiple threads. | #Use a "friendly" blocking mechanism that periodically polls the user input and updates display. This is no better than cooperative single-thread designs though, as it has slow response times and doesn't scale well to multiple threads. | ||
#Build your entire GUI around "messages" and "callbacks" (sometimes also called "signals"). This is the most flexible and user-friendly option but can add a lot of "framework" to any codebase. | #Build your entire GUI around "messages" and "callbacks" (sometimes also called "signals"). This is the most flexible and user-friendly option but can add a lot of "framework" to any codebase. | ||
| Line 24: | Line 22: | ||
The second one is in fact the recommended design by Microsoft, and one they've been using for almost everything in Windows ever since Win95. It's one of the reasons the Win32 API feels "heavy" to a lot of programmers, but as it turns out, it's not without good reason. | The second one is in fact the recommended design by Microsoft, and one they've been using for almost everything in Windows ever since Win95. It's one of the reasons the Win32 API feels "heavy" to a lot of programmers, but as it turns out, it's not without good reason. | ||
{{PCSX2 Documentation Navbox}} | |||