Re: Background Processing in an MFC application
I see that Scott has suggested that you use a timer to check whatever
criteria you need for this sort of thing. You could, for example, check
every 5 seconds to see if file arrived in your queue folder (don't know
exactly what you are doing). If the file is being sent by some event that
you can catch (user presses key, another window could send a message, etc.)
that would be better.
If the files are .PDFs you could open the Adobe Reader using
ShellExecuteEx() and just passing the .PDF type file. The shell will figure
out what to use and open the file appropriately. You could even check to
see if the ShellExecuteEx() call fails and suggest to the user that they
download the code for this functionality.
This is true, of course, unless you're trying ot open Adobe Reader as a
window in your own program. It may simplify your problem if you just let it
run as a separate application.
Tom
"KeepFaith" <vadnala@gmail.com> wrote in message
news:1181087756.165304.36630@n4g2000hsb.googlegroups.com...
Hello All,
I am newbie and need some help as I am stuck and spent enough time to
no avail. I have an existing MFC application which has a "Dialog"
listing few files. In this dialog, there is a button (Delete) which on
click deletes the selected files.
Now, I want to do some background processing where the user will never
open the above dialog but wants these files deleted as they come in
without any user interaction.
I thought of doing this by running a THREAD (Named Pipe) in the
background. But at some time I also need to open "Adobe Reader" using
"CreateDispatch" which fails with an error 14007 (from GetLastError).
So, is there a better way of doing this? Appreciate your enlightenment
and your time. Awaiting for a kind reply.
Best Regards,
KF