Re: printing support, CFormView base class
- From: "Tom Serface" <tserface@xxxxxxx>
- Date: Tue, 27 Sep 2005 23:25:02 -0700
That still works. You can simply cut and paste in the print "stuff" and
create the report manually, but when doing a CFormView most people wanted to
print the "screen" and it was confusing that they couldn't so, my guess is
that MSFT just put that warning up to, um, warn people that it didn't work.
I can't argue with your logic though. It didn't hurt putting in the
framework even though it didn't really print the form. I used it that way
as well and now I just put the stuff in by hand.
Tom
"Roger" <Roger@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:93878DD4-CC0B-40B3-BC10-72F4FF8A8B11@xxxxxxxxxxxxxxxx
>I assume you mean that the built in calls don't do anything to help print
>the
> graphic representation of the form itself. However my objective is to
> some reports that are largely text based. The framework provided by the
> built in calls helped my do exactly that in VS6 when I wrote my first MFC
> application. I would have been more adrift without that framework and
> that's
> why I'm wondering why it is not included when I create a project with VS7.
>
> "Tom Serface" wrote:
>
>> Well, sort of. The built in calls to printing really didn't do anything
>> for
>> Form Views in 6.0 and I think they were just trying to make that clear in
>> 7.x since it was always a point of confusion. However you can use
>> techniques like in this article to get what you want:
>>
>> http://www.codeproject.com/printing/printformview.asp
>
.
- References:
- printing support, CFormView base class
- From: The Other Roger
- Re: printing support, CFormView base class
- From: Tom Serface
- printing support, CFormView base class
- Prev by Date: Re: How to Read typed text
- Next by Date: Re: CButton & CStatic (special characters)
- Previous by thread: Re: printing support, CFormView base class
- Next by thread: RE: printing support, CFormView base class
- Index(es):