C / C++ / MFC

19-Apr-03 6:32

Hi,

I am trying desperately to print a report in Landscape
Mode with VC++, but even I try with "hDevMode" ... it
still always print in Portrait Mode:

<br />
    CPrintDialog printDlg(FALSE, PD_RETURNDEFAULT | PD_RETURNDC);<br />
<br />
    if (printDlg.DoModal() == IDCANCEL)     return; <br />
<br />
    ////////////////// Landscape Mode //////////////////////<br />
<br />
    HGLOBAL m_hDevMode;<br />
    HGLOBAL m_hDevNames;<br />
<br />
    PRINTDLG   pd;<br />
    pd.lStructSize = (DWORD) sizeof(PRINTDLG);<br />
<br />
    // Lock memory handle.<br />
    DEVMODE FAR* pDevMode =<br />
        (DEVMODE FAR*)::GlobalLock(m_hDevMode);<br />
    LPDEVNAMES lpDevNames;<br />
    LPTSTR lpszDriverName, lpszDeviceName, lpszPortName;<br />
    HANDLE hPrinter;<br />
	<br />
    // pDevMode is not TRUE, program not going this LOOP<br />
    if (pDevMode)   <br />
    {<br />
        // Change printer settings in here.<br />
       pDevMode->dmOrientation = DMORIENT_LANDSCAPE;<br />
<br />
       // Unlock memory handle.<br />
       lpDevNames = (LPDEVNAMES)GlobalLock(pd.hDevNames);<br />
       lpszDriverName = (LPTSTR )lpDevNames + lpDevNames->wDriverOffset;<br />
       lpszDeviceName = (LPTSTR )lpDevNames + lpDevNames->wDeviceOffset;<br />
       lpszPortName   = (LPTSTR )lpDevNames + lpDevNames->wOutputOffset;<br />
<br />
       ::OpenPrinter(lpszDeviceName, &hPrinter, NULL);<br />
       ::DocumentProperties(NULL,hPrinter,lpszDeviceName,pDevMode,<br />
						   <br />
       pDevMode, DM_IN_BUFFER|DM_OUT_BUFFER);<br />
<br />
       // Sync the pDevMode.<br />
       ::ClosePrinter(hPrinter);<br />
       ::GlobalUnlock(m_hDevNames);<br />
       ::GlobalUnlock(m_hDevMode);<br />
    }<br />
<br />
    ///////////////////// Standrad Printing  /////////////////<br />
<br />
	CDC		dc;<br />
	CPrintInfo	Info;<br />
	CFont		oFont;<br />
<br />
	dc.Attach(printDlg.GetPrinterDC());   	<br />
        dc.SaveDC();					<br />
	dc.m_bPrinting = TRUE;<br />
<br />
	CString strTitle;                      <br />
	strTitle.LoadString(AFX_IDS_APP_TITLE);<br />
<br />
	DOCINFO di;                            	<br />
        ::ZeroMemory (&di, sizeof (DOCINFO));<br />
	di.cbSize = sizeof (DOCINFO);<br />
	di.lpszDocName = strTitle;<br />
<br />
	BOOL bPrintingOK = dc.StartDoc(&di);  <br />
        ....................................<br />
        ....................................<br />

Can any one know why? To show you my problem I can
send "my small project" if you provide me your Email
address

I appreciate a lot anyone try to help me here

Thanks

Paolo Messina19-Apr-03 9:20

Paolo Messina

19-Apr-03 9:20

From MSDN:

<big>CWinApp::GetPrinterDeviceDefaults 
BOOL GetPrinterDeviceDefaults( PRINTDLG* pPrintDlg );</big>
<br>
Example<br>

void CMyApp::SetLandscapeMode()
{
   PRINTDLG pd;
   pd.lStructSize=(DWORD)sizeof(PRINTDLG);
   BOOL bRet=GetPrinterDeviceDefaults(&pd);
   if(bRet)
   {
      // protect memory handle with ::GlobalLock and ::GlobalUnlock
      DEVMODE FAR *pDevMode=(DEVMODE FAR *)::GlobalLock(m_hDevMode);
      // set orientation to landscape
      pDevMode->dmOrientation=DMORIENT_LANDSCAPE;
      ::GlobalUnlock(m_hDevMode);
   }
}

Give it a try...

Paolo

------
Why spend 2 minutes doing it by hand when you can spend all night plus most of the following day writing a system to do it for you? - (Chris Maunder)

ATC19-Apr-03 11:33

19-Apr-03 11:33

Hi Paolo,

Thank you for your tip, I did try but when it comesto :

<br />
pDevMode->dmOrientation=DMORIENT_LANDSCAPE;<br />

a) I had an Error & could not continue! I attach my small project
PrintLandscape.zip & did send to you ... so that you can see the problem!

b) When I ran debugging until this ,I recognized that pDevMode equals
Zero's ... might be I did not initiallize right?

Can you help a bit more?

Many thanks

Paolo Messina19-Apr-03 11:55

Paolo Messina

19-Apr-03 11:55

Hi,

I didn't get your attachment yet, but are you sure to call CWinApp::SelectPrinter after showing the dialog box?

Paolo

------
Why spend 2 minutes doing it by hand when you can spend all night plus most of the following day writing a system to do it for you? - (Chris Maunder)

ATC19-Apr-03 12:36

19-Apr-03 12:36

Hi Paolo,

I did reply but with error return! I have just sent to you another one (my small project) with your true Email address. Would you please take a look.

Many thanks,

ATC

Bartosz Bien20-Apr-03 4:41

Bartosz Bien

20-Apr-03 4:41

You may send it to me too (mail@BartoszBien.com) if not solved yet.

Happy Easter!
BB

ATC20-Apr-03 5:34

Re: With your helps, it works now!

20-Apr-03 5:34

Hi Bart,

Thank for the offer, I did send ny project to your Email address! Hopefully, you can help me! I have been stuck for this problem very long time! I really appreciate any help from anyone.

Many thanks & Happy Eastern,

Anh

ATC22-Apr-03 9:03

SplitterWnd - Moving the bar

22-Apr-03 9:03

Hi Paolo,

What should I say ... THANK YOU VERY VERY MUCH! I just did as you suggested: CWinApp::CreatePrinterDC (after seting pDevMode) & now I can print in Landscape even the Control Panel was set with Portrait

I am really appreciate a lot what you have tried to help me! I am sorry about asking you spent a lot of time to solve my problem ... but you do not know how I happy I am now ... because of your help!

Thanks again Paolo & please forgive me if I make you frustrated!

Sincerely yours,

Anh Big Grin | :-D

Shutter19-Apr-03 5:26

Shutter

19-Apr-03 5:26

Hiya,

I have a CSplitterWndEx class derived from CSplitterWnd. I have these two functions to only allow the user to move the bar so that the right pane is between 100 & 200 px wide. I have a variable called m_ULWidth in the CMainFrame class, which stores the width of the pane. It works fine, except for two things...

1) When I minimize and restore the app, the width of the pane reverts back to 150 px (what I initialized it to in the constructor)

2) If I keep clicking and dragging the splitter towards the right, it will still move a few pixels to the right each time even though the pane is at 100 pixels wide.

int CSplitterWndEx::GetSplitterWidth(void)<br />
{<br />
	return m_cxSplitterGap + (m_cxBorder * 2);<br />
}

void CSplitterWndEx::OnMouseMove(UINT nFlags, CPoint point)<br />
{<br />
	CRect rect;<br />
	this->GetParentFrame()->GetWindowRect(rect);<br />
	ScreenToClient(rect);<br />
	<br />
	if (point.x > (rect.right - 200) && point.x < (rect.right - 100)) <br />
		CSplitterWnd::OnMouseMove(nFlags, point);<br />
}

void CMainFrame::OnSizing(UINT fwSide, LPRECT pRect)<br />
{<br />
<br />
	CFrameWnd::OnSizing(fwSide, pRect);<br />
	CRect rect;<br />
	int width, ideal;<br />
	m_wndSplitterLR.GetColumnInfo(1,width, ideal);<br />
	m_ULWidth = width;<br />
}

void CMainFrame::OnSize(UINT nType, int cx, int cy)<br />
{<br />
	CFrameWnd::OnSize(nType, cx, cy);<br />
<br />
	if(m_ULWidth < 100)<br />
		m_ULWidth = 100;<br />
	if(m_ULWidth > 200)<br />
		m_ULWidth = 200;<br />
<br />
	if (  m_bInitSplitter && nType != SIZE_MINIMIZED )<br />
	{<br />
		m_wndSplitterLR.SetColumnInfo( 0, cx - m_ULWidth - m_wndSplitterLR.GetSplitterWidth(), 100);<br />
		m_wndSplitterLR.SetColumnInfo( 1, m_ULWidth, 75);<br />
		m_wndSplitterLR.RecalcLayout();<br />
<br />
	}

Any suggestions? Smile | :)

Shutter

Question about const pointer.

George219-Apr-03 4:04

George2

19-Apr-03 4:04

Hi, everyone!

When using pointers, we often meet with such troubles,
one problem is the ownership - who (which function)
is responsible for deleting the pointer? Another problem is
there's no standard way that you can tell if a pointer points
to the heap or to the stack. If it's to the heap, then
you can delete it; if it points to the stack, then you'd better
not use delete on the pointer.

I have searched some materials on the problem. One solution others
suggested is using const pointer (for example, int * const). But I do
not understand why it can resolve the trouble. (Other solutions include
smart pointers and reference.)

Can anyone show me an example?

Thanks in advance,
George

John M. Drescher19-Apr-03 5:01

John M. Drescher

19-Apr-03 5:01

I think this is more of an academic discussion than something you will do in your profession. In the last 6 years I have written 300 thousand lines of code and I have never for a minute thought about any of this discussion. If a function is passed a pointer 99.99% of the time the function should not delete it. If a function returns a pointer the documentation should describe how to delete it. There is more than just on the stack or heap. You can allocate memory with new, malloc, through COM or one of the VirtualAlloc functions. Deleting it with the wrong one will lead to problems.

John

George219-Apr-03 18:17

George2

19-Apr-03 18:17

Thanks, John buddy!

George

Phil Hamer19-Apr-03 16:44

Phil Hamer

19-Apr-03 16:44

I remember reading in Scott Meyers' book More Effective C++ that it's basically impossible to tell from just a pointer whether it points into the heap or elsewhere. And on deciding who deletes the pointer, this can probably best be achieved with comments. I do not see how const pointer would help.