Forum

Hi

I want to appoint print pages in CExtPPVW.

Thank you.

This feature is already implemented in the CExtPPVW template class. There are two new flag properties

- if a new CExtPPVW::m_bUsePrintDialogFromOutside flag is set to true, you can see the print dialog with the page number editor when command ID_FILE_PRINT is invoked from outside the print preview subsystem.

- if a new CExtPPVW::m_bUsePrintDialogFromPreview flag is set to true, then you can see the print dialog with the page number editor when command ID_FILE_PRINT is invoked from the toolbar at the top of the print preview window.

Both flags are set to false by default. Please contact us via email if you need this update right now.

Hi

Please send a thing of new Version.

x956123@yahoo.co.jp

The zipped source code takes up about 13Mb so we can only offer you to download from our ftp site. Please contact us via email for details.

Hi

>The zipped source code takes up about 13Mb so we can only offer you to download from our ftp site. Please contact us via email for details.

Where should I download it from?

Hi

Assert comes out.
Or there is a case to fall when I cancel it with a print dialog screen.

Is this a bug? (-0-;)

An example:
ASSERT(m_pd.Flags & PD_ENABLEPRINTHOOK);
ASSERT(m_pd.Flags & PD_ENABLESETUPHOOK);

Could you show us the content of the call stack window when the assertion occurs?

Hi

This Is Call Stack.

A pattern (1)

Assert ------------> CPrintDialog::DoModal() line 259 + 37 bytes
Assert ------------> CExtPPVW_Printable::DoPrintDoc(int 1) line 1018 + 45 bytes
CExtPPVW_HostWnd::OnPreviewPrint() line 3364 + 48 bytes
_AfxDispatchCmdMsg(CCmdTarget * 0x026d14d0 {CExtPPVW_HostWnd}, unsigned int 30570, int 0, void (void)* 0x005a3b4c CExtPPVW_HostWnd::OnPreviewPrint(void), void * 0x00000000, unsigned int 12, AFX_CMDHANDLERINFO * 0x00000000) line 88
CCmdTarget::OnCmdMsg(unsigned int 30570, int 0, void * 0x00000000, AFX_CMDHANDLERINFO * 0x00000000) line 302 + 39 bytes
CView::OnCmdMsg(unsigned int 30570, int 0, void * 0x00000000, AFX_CMDHANDLERINFO * 0x00000000) line 162 + 24 bytes
CWnd::OnCommand(unsigned int 30570, long 0) line 2099
CWnd::OnWndMsg(unsigned int 273, unsigned int 30570, long 0, long * 0x0012f43c) line 1608 + 28 bytes
CWnd::WindowProc(unsigned int 273, unsigned int 30570, long 0) line 1596 + 30 bytes
CExtPPVW_HostWnd::WindowProc(unsigned int 273, unsigned int 30570, long 0) line 2785 + 23 bytes
AfxCallWndProc(CWnd * 0x026d14d0 {CExtPPVW_HostWnd hWnd=???}, HWND__ * 0x00040384, unsigned int 273, unsigned int 30570, long 0) line 215 + 26 bytes
AfxWndProc(HWND__ * 0x00040384, unsigned int 273, unsigned int 30570, long 0) line 379
AfxWndProcBase(HWND__ * 0x00040384, unsigned int 273, unsigned int 30570, long 0) line 220 + 21 bytes
USER32! 77cf8734()
USER32! 77cf8816()
USER32! 77cfb4c0()
USER32! 77cfb50c()
NTDLL! 7c94eae3()
USER32! 77d0f3e3()
CExtCmdItem::Deliver(HWND__ * 0x00040384, unsigned char 1) line 420 + 27 bytes
CExtCmdItem::Deliver(CControlBar * 0x027016b8 {CExtPPVW_ToolBar hWnd=???}, unsigned char 1) line 481 + 29 bytes
CExtBarButton::OnDeliverCmd() line 4030 + 22 bytes
CExtBarButton::OnClick(CPoint {x=743 y=18}, unsigned char 0) line 3995 + 16 bytes
CExtToolControlBar::OnLButtonUp(unsigned int 0, CPoint {x=743 y=18}) line 11341 + 26 bytes
CWnd::OnWndMsg(unsigned int 514, unsigned int 0, long 1180391, long * 0x0012fa40) line 1975
CWnd::WindowProc(unsigned int 514, unsigned int 0, long 1180391) line 1596 + 30 bytes
CControlBar::WindowProc(unsigned int 514, unsigned int 0, long 1180391) line 480 + 20 bytes
CExtControlBar::WindowProc(unsigned int 514, unsigned int 0, long 1180391) line 8535
CExtToolControlBar::WindowProc(unsigned int 514, unsigned int 0, long 1180391) line 12795
CExtPPVW_ToolBar::WindowProc(unsigned int 514, unsigned int 0, long 1180391) line 1534 + 20 bytes
AfxCallWndProc(CWnd * 0x027016b8 {CExtPPVW_ToolBar hWnd=???}, HWND__ * 0x00030386, unsigned int 514, unsigned int 0, long 1180391) line 215 + 26 bytes
AfxWndProc(HWND__ * 0x00030386, unsigned int 514, unsigned int 0, long 1180391) line 379
AfxWndProcBase(HWND__ * 0x00030386, unsigned int 514, unsigned int 0, long 1180391) line 220 + 21 bytes
USER32! 77cf8734()
USER32! 77cf8816()
USER32! 77cf89cd()
USER32! 77cf96c7()
CWinThread::PumpMessage() line 853
CWinThread::Run() line 487 + 11 bytes
CWinApp::Run() line 400
AfxWinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x00151f08, int 1) line 49 + 11 bytes
WinMain(HINSTANCE__ * 0x00400000, HINSTANCE__ * 0x00000000, char * 0x00151f08, int 1) line 30
WinMainCRTStartup() line 330 + 54 bytes


A pattern (2)


NTDLL! 7c941230()
Assert ------------> _CrtDbgReport(int 2, const char * 0x5f4d1014 THIS_FILE, int 916, const char * 0x00000000, const char
Assert ------------> CPreviewDC::MirrorViewportOrg() line 916 + 40 bytes
CPreviewDC::MirrorMappingMode(int 0) line 908
CPreviewDC::SetOutputDC(HDC__ * 0x59010d37) line 132
CExtPPVW_HostWnd::OnDraw(CDC * 0x0012de4c {hDC=??? attrib=???}) line 2810 + 40 bytes
CExtPPVW_HostWnd::WindowProc(unsigned int 15, unsigned int 0, long 0) line 2705 + 26 bytes
AfxCallWndProc(CWnd * 0x026f1028 {CExtPPVW_HostWnd hWnd=???}, HWND__ * 0x00050380, unsigned int 15, unsigned int 0, long 0) line 215 + 26 bytes
AfxWndProc(HWND__ * 0x00050380, unsigned int 15, unsigned int 0, long 0) line 379
AfxWndProcBase(HWND__ * 0x00050380, unsigned int 15, unsigned int 0, long 0) line 220 + 21 bytes
USER32! 77cf8734()
USER32! 77cf8816()
USER32! 77cfb4c0()
USER32! 77cfb50c()
NTDLL! 7c94eae3()
USER32! 77cf96c7()
CWinThread::PumpMessage() line 853
CExtPPVW_Printable::stat_PrintingAbortProc(HDC__ * 0x02210d49, HDC__ * 0x02210d49) line 757 + 21 bytes
GDI32! 77f03943()
GDI32! 77f0496c()
GDI32! 77f04b56()
CDC::StartDocA(_DOCINFOA * 0x0012ec74) line 906 + 62 bytes
CExtPPVW_Printable::DoPr


Second Chance Assertion Failed: File dcprev.cpp, Line 916
Second Chance Assertion Failed: File dcprev.cpp, Line 964

Using the SimpleGrids sample, we failed to reproduce the assertion failures you posted above as you can see this on this figure.

Would you tell us if these these call stack listings were produced by some of our sample applications or by your project?

We guess the problem may be hidden somewhere outside our samples. For example, once we encountered a problem that was specific to HP 1022 drivers that crashed when 32-bit BMP images were printing as graphic items inside enhanced metafile data. Would you try to find any additional information which may help us clarify what’s wrong? Of course, after all, we could debug the problem remotely with remote desktop.

Hi

>Would you tell us if these these call stack listings were produced by some of our sample applications or by your project?

It occurred in SimpleGirds.
1,
2, A print button click.
3, I appoint the print number of sheets.
4, Assert

>you try to find any additional information which may help us clarify what’s wrong?
For example, how?

Are you to want to do "Remote Debug" of my PC???

We would like to ask one more detail: Visual Studio version and its Service Pack number you are using if any. We have checked the printing and print preview in the SimpleGrids sample compiled with Visual Studio 6.0 and Visual Studio 2005 without any service pack and no assertions occurred.

>>Are you to want to do "Remote Debug" of my PC???
Yes, we could connect to your desktop remotely so you can demonstrate the problem on spot.

Hi

>Visual Studio version and its Service Pack number you are using if any. We have checked the printing and print preview in the
>SimpleGrids sample compiled with Visual Studio 6.0 and Visual Studio 2005 without any service pack and no assertions occurred

About movement environment.

PC ( Dell Optiplex gx270 )

Visual Studio V6 Service Pack number 6
http://www.microsoft.com/downloads/details.aspx?FamilyId=A8494EDB-2E89-4676-A16A-5C5477CB9713&displaylang=ja
Windows XP Service Pack 1

PC ( Dell C521 )

Visual Studio 2003 .NET ( There is not a Service Pack )
Windows XP Service Pack 2
OR
Visual Studio V6 Service Pack number 6
Windows XP Service Pack 2

Printer
Epson LP-9800C
Xerox DocuCenter 250/350/400

All was no use.

>Yes, we could connect to your desktop remotely so you can demonstrate the problem on spot.
Do I have to install a module here to do "Remote Debug"?



　I try to test even a home PC.

If it was the following environment, I was able to print it first of all.

But 25 times of "Assert" appears.

PC (Deminsion 2400)

Windows XP

Visual Studio 2003 .NET ( There is not a Service Pack )
OR
Visual Studio V6 Service Pack number 6

Simple-Girds-md.exe ( M Debug )

Printer
Canon MP-950

We sent you the details about remote debuging by email.

HI

I prepare for environment.
Please wait.

When you are ready, please contact us via email at support@prof-uis.com.

Hi

I prepared.
Please test it.

In addition, the time that you can take advantage of.
04/19-10:00 ～ 04/19-19:00 (American Time)
If more debug is necessary, please answer it.

Then please do not read a private thing if possible.

I made a mistake in a date.

04/12-10:00 ～ 04/12-19:00 (American Time)
If more debug is necessary, please answer it.

Hi

I was able to print it rightly.

Thank you.