I need to write an MFC Dialog-based application that has no buttons, but
determines what it needs to do from command line parameters, and then
displays some things in a textbox.  After it's done, it should just
exit.

Some questions:

1) Using AppWizard, how do I create such an application?  Can I just
create the Dialog application using the wizard, then simply delete the
OK and Cancel buttons?

2) As far as the code that I need to implement to evaluate the command
line parameters and then perform the work (some calculations and then
display), where's the "right" place to put this code, especially since I
won't have any "Onbutton..." functions, etc.?

Should I put it in OnInitInstance?

My apologies if these are somewhat unusual questions...

Jim

That seems reasonable to me.

Dave
--
MVP VC++ FAQ: http://www.mvps.org/vcfaq
My address is altered to discourage junk mail.
Please post responses to the newsgroup thread,
there's no need for follow-up email copies.

I would simply do a GetCommandLine() [I think that's the API; I haven't used a command
line in years] in the OnInitDialog handler. OnInitInstance is far too soon, since the
dialog has not yet been created until the DoModal(), and after the DoModal() returns it is
too late.
                                joe

--
Bob Moore [WinSDK MVP]
http://www.mooremvp.freeserve.co.uk/
(this is a non-commercial site and does not accept advertising)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Do not reply via email unless specifically requested to do so.
Unsolicited email is NOT welcome and will go unanswered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Yes - the exit is determined via a timer, which is somewhat determined
by the command line parameter...