My main question at this point is how/why calling PrintDlg() based on input from an application window would cause that window to not get its focus back after dismissing the print dialog box. More before dropping trace information on you in this forum, but I will probably do that to you eventually if I can't find the cause for the problem. I've been adding tracing capability to QuickWin and can compare the "works" with the "doesn't work" results, and I can see that WM_SETFOCUS messages are not present in the version that does not work.
#Simply fortran windows dialogs code#
This code was originally put together decades ago (and not be me, btw -)
#Simply fortran windows dialogs windows 7#
While investigating that Windows 7 problem I became a believer that attaching all If I simply bring the AttachThreadInput() call back to life, everything is fine. So that messages sent to a particular window's procedure went to the same place. Before that change all threads that QuickWin created, and there is always a minimum of two, were attached
Let me be clear, that this is, well, my "fault", for fixing QuickWin's original problem to deal with changes in the Windows 7 message handler. This occurs on Windows 7 and XP, on both x86 and 圆4. This is all C and Fortran, and as I hinted at above, is the result of a major change in how our Fortran's QuickWin library operates. I know, I know, nobody out there is "into" Fortran, but I don't believe that Fortran is the issue here. But I can't understand how putting this dialog box up messes up the focus of the application window. I can understand how thousands of lines of code that used to rely on joining all input queues might have some problems when they are no longer joined. If I reverse the AttachThreadInput change it works fine. You can click to another window (uhh, like VS debugger) and then click in the application
However, after hitting CANCEL (or PRINT for that matter), the original application windows does not get the focus back, even though it appears to be in the foreground. Given that change, we now have a Fortran program that uses PrintDlg to put up a print dialog box. We have a Windows layer for Fortran that has been around for many years (and with a number of companies as the industry compressed) that used to use AttachThreadInput() to join all threads into a single queue.
0 kommentar(er)
