PCSX2 Documentation/The PCSX2 Program Flow: Difference between revisions

no edit summary
No edit summary
Line 2: Line 2:


==AppMain.cpp - this is where the fun begins!==
==AppMain.cpp - this is where the fun begins!==
There is a lot that happens under the hood with wxWidgets. We don't need to worry about that. All we need to worry about is this this line of code in [https://github.com/PCSX2/pcsx2/blob/master/pcsx2/gui/AppMain.cpp AppMain.cpp].
There is a lot that happens under the hood with wxWidgets. We don't need to worry about that. All we need to worry about is this this line of code:
 
'''[https://github.com/PCSX2/pcsx2/blob/master/pcsx2/gui/AppMain.cpp AppMain.cpp]'''
<source lang="cpp">IMPLEMENT_APP(Pcsx2App)</source>
<source lang="cpp">IMPLEMENT_APP(Pcsx2App)</source>
This macro tells the wxWidgets framework that we want to fire up Pcsx2App. Easy, right?
This macro tells the wxWidgets framework that we want to fire up Pcsx2App. Easy, right?


Line 15: Line 18:
if( m_UseGUI ) OpenMainFrame();
if( m_UseGUI ) OpenMainFrame();
</source>
</source>


==WxWidgets Frames==
==WxWidgets Frames==


In addition to Application classes, there are also Frame classes. So when we call the OpenMainFrame function, what happens? Take a look at this code:
In addition to Application classes, there are also Frame classes. So when we call the OpenMainFrame function, what happens? Take a look at this code:


'''[https://github.com/PCSX2/pcsx2/blob/master/pcsx2/gui/AppInit.cpp pcsx2/gui/AppInit.cpp]'''
'''[https://github.com/PCSX2/pcsx2/blob/master/pcsx2/gui/AppInit.cpp pcsx2/gui/AppInit.cpp]'''
ninja
782

edits