Re: Printing Problems
- From: "Nicholas Paldino [.NET/C# MVP]" <mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 2 Dec 2005 15:02:48 -0500
Unfortunately, yes, that is exactly what I mean. You will have to store
that on some level, and then access it later from the delegate that handles
the actual printing (or before you start printing, depending on the
property).
--
- Nicholas Paldino [.NET/C# MVP]
- mvp@xxxxxxxxxxxxxxxxxxxxxxxxxxx
<MLM450@xxxxxxxxxxx> wrote in message
news:1133544606.276809.169720@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> Thanks for the quick reply Nicholas.
>
> Forgive me if this sounds like a stupid question, but can you expand on
> what you mean by "expose whatever properties were set"? We are
> using the PRINTDLG structure with the standard print dialog. Do you
> mean I need to go through all the PRINTDLG, DEVMODE, and DEVNAMES items
> and transfer all this information manually? (yuck)
>
.
- Follow-Ups:
- Re: Printing Problems
- From: MLM450
- Re: Printing Problems
- References:
- Printing Problems
- From: MLM450
- Re: Printing Problems
- From: Nicholas Paldino [.NET/C# MVP]
- Re: Printing Problems
- From: MLM450
- Printing Problems
- Prev by Date: Re: Coding an application to be single instance?
- Next by Date: Re: Serialize A Dictionary
- Previous by thread: Re: Printing Problems
- Next by thread: Re: Printing Problems
- Index(es):
Relevant Pages
|