Oops... I mean document <blush> slip...
"Joseph M. Newcomer" <newcomer@flounder.com> wrote in message
I think the OP is merely confusing data and presentation. Therefore,
persists in the
notion that data == presentation and if you delete the presentation you
must therefore
delete the data. Then he denies the usability of the document because
"all the work is
done in a DLL", not realizing that the DOCUMENT is the place to keep the
DATA!
In fact, I even question why "the view does the maths" when in fact the
COMPUTATION should
be in the document! The view is merely a minor and relatively trivial
conceptual piece of
the effort, a mere way of presenting data. It is a fundamental
misunderstanding of the
relationship of view and document, mistaking presentation for data.
Therefore, instead of creating a totally trivial solution, he persists in
trying to create
bizarre, complex solutions to what is a trivial problem.
joe
On Thu, 21 Jun 2007 07:18:38 -0700, "Tom Serface"
<tom.nospam@camaswood.com> wrote:
Could you just hide the child frame window rather than close it and thus
retain both objects? You should be able to use ShowWindow(SW_HIDE).
Tom
"GT" <ContactGT_remove_@hotmail.com> wrote in message
news:00b21682$0$2842$c3e8da3@news.astraweb.com...
I have my own pointer to a view:
ViewResourceLoadChart *m_viewResourceLoadingChart;
I create in my code. the view is attached to a CChildFrame, but when I
call close on a childframe (pChild->SendMessage(WM_CLOSE);), it destroys
the view as well. How can I retain my view for future use?
Joseph M. Newcomer [MVP]
email: newcomer@flounder.com
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm