WS_POPUP style windows
-
Hi, I have got a very basic question. Do WS_POPUP style windows get created in a separate thread than the thread which created them or do they run in the same thread and somehow also manage a message loop? Thanks,
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
-
Hi, I have got a very basic question. Do WS_POPUP style windows get created in a separate thread than the thread which created them or do they run in the same thread and somehow also manage a message loop? Thanks,
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
-
HakunaMatada wrote:
Do WS_POPUP style windows get created in a separate thread
no. When you call createwindow() from a thread, what ever be its style, it is created in same thread.
nave
Thanks for taking the time out to reply but I do have some more queries.
Naveen R wrote:
no. When you call createwindow() from a thread, what ever be its style, it is created in same thread.
If so, then what about the message loop. If I have a MainFrame window which in turn is creating 5 Popup windows, I believe that every window will have its own message loop. How does it maintain 6 message loops within the same thread? Thanks.
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
-
Thanks for taking the time out to reply but I do have some more queries.
Naveen R wrote:
no. When you call createwindow() from a thread, what ever be its style, it is created in same thread.
If so, then what about the message loop. If I have a MainFrame window which in turn is creating 5 Popup windows, I believe that every window will have its own message loop. How does it maintain 6 message loops within the same thread? Thanks.
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
HakunaMatada wrote:
I believe that every window will have its own message loop
No. Only one meesage loop will be there. When a window is created, there will no message loop. we have to explicitly write the message after creating the function( MFC is internally doing this). In the MainFrame case you said the sequence will be... 1. Create MainFrame 2. Create 5 popup window 3. Start the message loop
while( GetMessage())// this loop is normally called as message loop { TranslateMessage(); DispatchMessage(); }you can find this message loop in the CWinThread::PumpMessage() function.nave
-
HakunaMatada wrote:
I believe that every window will have its own message loop
No. Only one meesage loop will be there. When a window is created, there will no message loop. we have to explicitly write the message after creating the function( MFC is internally doing this). In the MainFrame case you said the sequence will be... 1. Create MainFrame 2. Create 5 popup window 3. Start the message loop
while( GetMessage())// this loop is normally called as message loop { TranslateMessage(); DispatchMessage(); }you can find this message loop in the CWinThread::PumpMessage() function.nave
So, what you are saying is that there is just one message loop which gets created and the framework makes it seem like all have separate message loops? Lets say for example... 1) Create MainFrame. 2) Run Message Loop. 3) Create 5 Popup windows on an event, say button click. Lets say the classes for the Mainframe and Popup windows are CMainFrame, CPopup1, CPopup2.... etc. All classes have their own message loops(BEGIN_MSG_MAP and END_MSG_MAP). Does the framework being used make us think that separate message loops are being used when in reality only message loop is being used or is the case otherwise? Thanks again for the answers.
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
-
So, what you are saying is that there is just one message loop which gets created and the framework makes it seem like all have separate message loops? Lets say for example... 1) Create MainFrame. 2) Run Message Loop. 3) Create 5 Popup windows on an event, say button click. Lets say the classes for the Mainframe and Popup windows are CMainFrame, CPopup1, CPopup2.... etc. All classes have their own message loops(BEGIN_MSG_MAP and END_MSG_MAP). Does the framework being used make us think that separate message loops are being used when in reality only message loop is being used or is the case otherwise? Thanks again for the answers.
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
HakunaMatada wrote:
All classes have their own message loops(BEGIN_MSG_MAP and END_MSG_MAP)
BEGIN_MSG_MAP and END_MSG_MAP are not message loop, they are message maps. The function added between that macro will be called by the MFC framework when a message of corresponing type arrives in that window. The better method to explorer this type of thing is to step in to the code of MFC while debugging.
nave
-
Hi, I have got a very basic question. Do WS_POPUP style windows get created in a separate thread than the thread which created them or do they run in the same thread and somehow also manage a message loop? Thanks,
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
HakunaMatada wrote:
o WS_POPUP style windows get created in a separate thread than the thread which created them or do they run in the same thread
Windows styles (like WS_POPUP) and threads are orthogonal concepts. WS_POPUP is about adorning your window (and maybe raising expectations in the user of your window). What you want to learn about is worker threads and UI threads! Maybe this[^] helps?
Failure is not an option - it's built right in.
-
HakunaMatada wrote:
All classes have their own message loops(BEGIN_MSG_MAP and END_MSG_MAP)
BEGIN_MSG_MAP and END_MSG_MAP are not message loop, they are message maps. The function added between that macro will be called by the MFC framework when a message of corresponing type arrives in that window. The better method to explorer this type of thing is to step in to the code of MFC while debugging.
nave
Thanks for the info.
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."
-
HakunaMatada wrote:
o WS_POPUP style windows get created in a separate thread than the thread which created them or do they run in the same thread
Windows styles (like WS_POPUP) and threads are orthogonal concepts. WS_POPUP is about adorning your window (and maybe raising expectations in the user of your window). What you want to learn about is worker threads and UI threads! Maybe this[^] helps?
Failure is not an option - it's built right in.
Thanks.
--- :beer: Hakuna-Matada :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."