|
Why are you using pParentWnd->GetSafeHwnd() to get your HWND? You should just use GetSafeHwnd() on its own.
|
|
|
|
|
thing is I don't know how the code got to dlgcore.cpp The Hwnd is a MainWindow
Okay thanks
|
|
|
|
|
It gets to dlgcore by virtue of your call to SendNotifyMessage, at which point it asserts because the handle you sent it is not valid.
|
|
|
|
|
But the Window Handle is a Main or Mainframe Window
I did a FindWindow api call
To get the handle As the parent is a C console app and it did work once before I created the modless dialog box in the child process
|
|
|
|
|
But you are calling pParentWnd->GetSafeHwnd() in a console app which makes no sense. What does pParentWnd point to?
|
|
|
|
|
Hi
I am at work now however the only thing I can think of at this point is that I have to use DuplicateHandle to make the child main window accessible to the parent
|
|
|
|
|
No, you just need to find its handle by one of the enumerate functions, or get the child to pass it back in some way. A handle is just a pointer used to identify a Window so you can send messages to it. To be honest, I am not exactly clear about what you are trying to do beyond the basic SendMessage function.
|
|
|
|
|
"EnumThreadWindows"
My questions in Windows is a threadID unique throughout Windows
Thanksp
|
|
|
|
|
I would assume yes, since in the case of EnumThreadWindows, the threadid is the only information Windows needs to return the information.
|
|
|
|
|
Richard got the same assertion I believe this has to do with sharing window handles between threads
I am going to use duplicate handle and see if that resolves the issue
Thanks
|
|
|
|
|
ForNow wrote: I believe this has to do with sharing window handles between threads
I don't think so. You should be able to send a message to a Window from anywhere.
|
|
|
|
|
I want to call an external application (created by me) using ShellExecute or CreateProcess. It is just an update application for the main app. The problem is, what ever I tried I failed to get window focus back to my main app when the process (update app) is terminated. I created a simple MFC/SDI app that calls window's notepad under "C:\windows\notepad.exe" which suffers from the same problem, just to show you what I mean. I need the parent window -which is the main app- to be disabled (like a modal dialog box behaviour) until the new app -update application- will finish its job.
PS:If I do not disable the main window with EnableWindow(FALSE) I have paint corruption with windows XP and back when I move the update application.
Here an example:
http://www.filedropper.com/shellexecutecreateprocesstestapp[^]
sdancer75
|
|
|
|
|
You could wait on the process handle returned by ShellExecute or CreateProcess, this will let you know when the child process has exited.
Then you could use BringWindowToTop to bring your main application window to the foreground.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Thank you for your answer.
As you can see in the code I am using WaitForSingleObject. I tried to use also the BringWindowToTop with no luck. What ever I tried I had no success.
sdancer75
|
|
|
|
|
sdancer75 wrote: As you can see ... What ever I tried I had no success.
We cannot see anything, you need to show your code and explain where it goes wrong.
|
|
|
|
|
|
But what is a problem for you to attach a piece of code to your post?
|
|
|
|
|
Hi,
No problem at all, I just gave all the code in the link. Anyway, I attach you the most important code from the sample app.
void CMainFrame::OnRunExternalApp() {
SHELLEXECUTEINFO lpExecInfo;
PROCESS_INFORMATION processInfo;
DWORD dwExitCode;
HANDLE hProcess = 0;
BOOL bResult;
LPTSTR strCmd;
strCmd = _T("");
bResult = StartupApplicationWithProcess (_T("C:\\Windows\\notepad.exe"), (LPTSTR)strCmd, &processInfo);
EnableWindow(FALSE);
if(bResult) {
WaitForSingleObject(processInfo.hProcess, INFINITE);
if (!GetExitCodeProcess(processInfo.hProcess, &dwExitCode)) {
}
CloseHandle( processInfo.hProcess );
CloseHandle( processInfo.hThread );
} else {
}
BringWindowToTop();
EnableWindow(TRUE);
}
sdancer75
|
|
|
|
|
|
I will give it a try but as you may already see, I am using the bringWindowToTop without success.
Thanx
sdancer75
|
|
|
|
|
Yes, I see.
But try it in the following order:
EnableWindow
SetForegroundWindow
SetActiveWindow
BringWindowToTop
|
|
|
|
|
Seems to work with one exception. I get a flicker since it instantly lose its focus and then regain it back....
sdancer75
|
|
|
|
|
One last thing. The EnableWindow(xxxx) do the mess in my situation. If I dont use this function I have to process the paint messages from the child window. In this case I think that
WaitForMultipleObjects will do the job in the XP case. Do you agree with this guess ?
.... or better i will give it a try right now.
sdancer75
|
|
|
|
|
No, WFMO is the same as WFSO (just waiting for more than one object; however I don't see any additional one in your problem description).
The usual way is move waiting in a worker thread to not block the main UI thread.
|
|
|
|
|
When the external update process should also update the executable of your main application, that must be terminated before the new exe file can be copyied. So there is no need to get the focus back.
A typical sequence for such a process:
- Ask the user if the update should be installed
- Perform closing tasks that are time consuming or require user interaction like closing open documents
- Start the update process
- Terminate your application
- The update process should check if there is a running instance of your application (after a short wait time) and terminate with an error if so
- The update process might restart your application
In another post you mentioned that you are using WaitForSingleObject to wait for the update process to be terminated. If you call that from within your main thread, your application's message loop is blocked so that paint events are not processed.
If you don't want to update the executable itself and must wait for the external process to be finished start the process from within a worker thread where you can call WaitForSingleObject without blocking the message loop. Use a global state variable indicating that the update is executing to disallow specific tasks of your application or just show a modal dialog that is closed automatically when the update has finished.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
