|
Best thing to do is a screen grab.
void CMachine::PrintWindow()
{
// show options
CMyPrintDialog PrintDlg(
FALSE,
PD_ALLPAGES | PD_USEDEVMODECOPIES | PD_NOPAGENUMS | PD_NOSELECTION |
PD_DISABLEPRINTTOFILE,
this);
int Response = 0;
Response = PrintDlg.DoModal();
if (Response == IDOK)
{
// get printer dc
HDC hPrinterDC =(HDC) 0;
hPrinterDC = PrintDlg.m_pd.hDC;
ASSERT(hPrinterDC != NULL);
CDC PrinterDC;
BOOL IsAttached = FALSE;
IsAttached = PrinterDC.Attach(hPrinterDC);
ASSERT(IsAttached);
// Set landscape
LPDEVMODE pDevMode = PrintDlg.GetDevMode();
pDevMode->dmFields |= DM_ORIENTATION;
pDevMode->dmOrientation = DMORIENT_LANDSCAPE;
PrinterDC.ResetDC(pDevMode);
// attempt to set abort procedure
int SetAbortProcStatus = 0;
// SetAbortProcStatus = PrinterDC.SetAbortProc( &AbortProc );
// attempt to start print job
DOCINFO DocInfo;
DocInfo.cbSize = sizeof(DOCINFO);
DocInfo.lpszOutput = NULL;
DocInfo.lpszDocName = "PDMW Windows Screen Print";
int StartDocStatus = 0;
StartDocStatus = PrinterDC.StartDoc(&DocInfo);
// if abort procedure set and print job started
if (SetAbortProcStatus >= 0 && StartDocStatus >= 0)
{
// start page
VERIFY(PrinterDC.StartPage() > 0);
// get the screen dc
HDC hScreenDC =(HDC) 0;
hScreenDC = ::GetDC(NULL);// CDC
ASSERT(hScreenDC != NULL);
CDC ScreenDC;
VERIFY(ScreenDC.Attach(hScreenDC));
// create screen device dependent (dd) bitmap
CRect tmp;
GetWindowRect(tmp);
// ClientToScreen(tmp);
// tmp.top -= ::GetSystemMetrics(SM_CYCAPTION);
int ScreenWidth = tmp.Width();// - ::GetSystemMetrics(SM_CXEDGE) * 4;// 0;
// ScreenWidth = ScreenDC.GetDeviceCaps( HORZRES );
int ScreenHeight = tmp.Height();// + ::GetSystemMetrics(SM_CYCAPTION);// - ::GetSystemMetrics(SM_CYEDGE) * 4;
//- ::GetSystemMetrics(SM_CYCAPTION);// 0;
// ScreenHeight = ScreenDC.GetDeviceCaps( VERTRES );
CBitmap ScreenBitmap;
VERIFY(ScreenBitmap.CreateCompatibleBitmap(
&ScreenDC,
ScreenWidth,
ScreenHeight
));
// copy image to screen dd bitmap
CDC MemDC;
VERIFY(MemDC.CreateCompatibleDC(&ScreenDC));
CBitmap* pOldBitmap = NULL;
pOldBitmap = MemDC.SelectObject(&ScreenBitmap);
ASSERT(pOldBitmap != NULL);
VERIFY(MemDC.BitBlt(
0,
0,
ScreenWidth,
ScreenHeight,
&ScreenDC,
tmp.left,
tmp.top,
SRCCOPY
));
// create device independent (di) bitmap
const int BitCount = 24;
long ImageSize = 0;
ImageSize =((((ScreenWidth * BitCount) + 31) & ~31) >> 3)
* ScreenHeight;
BYTE* pBitmapBits = NULL;
pBitmapBits = new BYTE[ImageSize];
ASSERT(pBitmapBits != NULL);
// copy image from screen dd bitmap to di bitmap
BITMAPINFO BitmapInfo;
BitmapInfo.bmiHeader.biSize = sizeof(BITMAPINFOHEADER);
BitmapInfo.bmiHeader.biWidth = ScreenWidth;
BitmapInfo.bmiHeader.biHeight = ScreenHeight;
BitmapInfo.bmiHeader.biPlanes = 1;
BitmapInfo.bmiHeader.biBitCount = BitCount;
BitmapInfo.bmiHeader.biCompression = BI_RGB;
BitmapInfo.bmiHeader.biSizeImage = ImageSize;
BitmapInfo.bmiHeader.biXPelsPerMeter = 0;
BitmapInfo.bmiHeader.biYPelsPerMeter = 0;
BitmapInfo.bmiHeader.biClrUsed = 0;
BitmapInfo.bmiHeader.biClrImportant = 0;
memset(&BitmapInfo.bmiColors[0], 0, sizeof(RGBQUAD));
VERIFY(GetDIBits(
ScreenDC.m_hDC,
(HBITMAP) ScreenBitmap,
0,
ScreenHeight,
(LPVOID) pBitmapBits,
&BitmapInfo,
DIB_RGB_COLORS
));
VERIFY(ScreenBitmap.DeleteObject());
VERIFY(MemDC.DeleteDC());
ScreenDC.Detach();
// if bitmap selection succeeded
if (pOldBitmap != NULL)
{
// copy di bitmap to printer
int PrinterWidth = 0;
PrinterWidth = PrinterDC.GetDeviceCaps(HORZRES);
int PrinterHeight = 0;
PrinterHeight = PrinterDC.GetDeviceCaps(VERTRES);
if (PrintDlg.m_bCheckFullPage)
{
VERIFY(StretchDIBits(
PrinterDC.m_hDC,
0,
0,
PrinterWidth,
PrinterHeight,
0,
0,
ScreenWidth,
ScreenHeight,
(LPVOID) pBitmapBits,
&BitmapInfo,
DIB_RGB_COLORS,
SRCCOPY
) != GDI_ERROR);
}
else
{
CString strFactor;
int dFactor;
// PrintDlg.m_EditMagnifyCtrl.GetWindowText(strFactor);
strFactor = PrintDlg.GetFactorText();
if (strFactor.IsEmpty())
dFactor = 1;
else
{
dFactor = atoi(strFactor);
if (dFactor < 1)
dFactor = 1;
}
VERIFY(StretchDIBits(
PrinterDC.m_hDC,
(PrinterWidth - ScreenWidth * dFactor) / 2,
(PrinterHeight - ScreenHeight * dFactor) / 2,
ScreenWidth * dFactor,
ScreenHeight * dFactor,
0,
0,
ScreenWidth,
ScreenHeight,
(LPVOID) pBitmapBits,
&BitmapInfo,
DIB_RGB_COLORS,
SRCCOPY
) != GDI_ERROR);
}
// finish the print job
VERIFY(PrinterDC.EndPage() >= 0);
VERIFY(PrinterDC.EndDoc() >= 0);
}
// else could not select bitmap
else
{
// abort job
VERIFY(PrinterDC.AbortDoc() >= 0);
AfxMessageBox("Could Not Print--Memory Error Possible.");
}
// clean up
delete pBitmapBits;
}
// else job cannot be started
else
{
// attempt to abort job
PrinterDC.AbortDoc();
AfxMessageBox("Cannot Start Print Job.");
}
// clean up
PrinterDC.Detach();
VERIFY(DeleteDC(hPrinterDC));
}
}
BOOL CALLBACK CMachine::AbortProc(HDC hdc, int iCode)
{
MSG msg;
while (!bUserAbort && PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
{
if (!hDlgPrint || !::IsDialogMessage(hDlgPrint, &msg))
{
TranslateMessage(&msg);
DispatchMessage(&msg);
}
}
if (iCode > 0)
bUserAbort = 1;
return !bUserAbort;
}
|
|
|
|
|
I have implemented an interface using ATL(in-proc server). In one of the interface methods, I display a modal dialog. The dialog is written in MFC. When this interface method and hence when the dialog class' DoModal() is called, there is a line of code in MFC libraries, that calls AfxGetInstanceHandle(). The function AfxGetInstanceHandle() ASSERTs if a variable by name afxCurrentInstanceHandle is not NULL. Unfortunately this variable is NULL. AfxGetInstanceHandle() is supposed to return the handle of the EXE. Am I doing things right?
|
|
|
|
|
At the beginning of the method, put this line:
AFX_MANAGE_STATE(AfxGetStaticModuleState());
to have MFC init its state information for your DLL. You need to do this in every exported function that can be called from outside the DLL.
|
|
|
|
|
I added this line as the first statement of the exported function (in my case an interface method). Unfortunately, I get a linker error that _DllMain@12 is already defined. DllMain is automatically generated for me when I added this ATL object to the project and is where I load the resource DLL for this component. But the linker includes mfcs42ud.lib as well where there is a second definition of DllMain. Moreover I guess that AFX_MANAGE_STATE is for REGULAR DLLs only. What do I do now?
|
|
|
|
|
|
How would I get an event for a key-stroke like ALT+SHIFT+CTRL+L even while the capture isn't on my program? Many programs (such as ICQ) do things like this.
|
|
|
|
|
Look up the RegisterHotKey() API.
|
|
|
|
|
I have a program which will generate Images of different objects on the screen.If you choose a menu item (RSC,Folder for example) you are promted to enter a few parametrs related to the object.(Length,Width,Depth and flute)
Since all of the objects need the same info I want to use one single dialog.However Each object manipulates the info in different ways..With a single dialog and hence a single
"Render" button how can I determine Which object the dialog was called for in my OnRender Function...Is what Im trying to do possible???It has to be this is C++  ).
Any suggestions or hints would be greatly appreciated...
Thanks for the time
J.Prisco
|
|
|
|
|
Make a base class for all the objects.
Put a member variable in it to represent the current ype.
Make an enumeration for all your types.
Derive all your 'object' classes from this base type.
Use the value of the 'type' data item to let your OnRender code know what was selected.
The diaog can also use that 'type' variable to know what controls to display to user, or else how to limit the data ranges where user might be entering numbers.
You could do the saem thing with C structures, always make the first element of the object structures this type.
Then if you have a pointer to some of this memory, you can cast the pointer to this 'type' variable and access the data structure's object type.
|
|
|
|
|
Although this sounds good Im still not to clear on how this is done..Thanks for the hint Ill investigate it further..
|
|
|
|
|
I assume that you have one menu item for each object that you want to display. I also assume that each kind of display object is being abstracted as a class and all these classes have a common base class. In the menu handler for each of these menu items, you would probably instantiate an object of the dialog class and call its DoModal(). You can pass a 'C++ object' of the appropriate object to be displayed to the dialog's constructor. In the dialog's OnRender() method, you can call the Render() method of these objects, provided the Render() method of the base class is virtual.
|
|
|
|
|
Well I made my initial post when I first discovered the problem .At my fist observation it really seemed to be quite a problem..After a little though I figured a way to do what I needed but in fact What I was planning wasnt even necisarry at all.Once I began coding the app I found the problem was no problem at all...For each menu item handler
I use DoModal and upon its return I assign the corresponding objects variables...Although a little inneficient it works just fine..
Thanks for the help I really appreciate all the help I can get and Ill probably need more help with this app which is probably a little too ambitious for me at this point.
|
|
|
|
|
Hi,
I have been trying to set the fontsize and fontface of a label control. Does anyone know how to do this in ATL? I am usnig the stock property "FONT", but I just can't get it to work. I have just about all the other properties doing what I want them to do, but font is really giving me a hard time.
Thanks
|
|
|
|
|
Hi,
There is a very nice step-by-step instructions in the MSDN article "FILE: Using Fonts in ATL Controls with NiceText.exe" Article ID: Q166472. I've used it about a year ago and it worked fine.
Regards,
Alex Gorev,
Dundas Software.
|
|
|
|
|
I am doing some stand-alone apps for handheld scanners. I need to know just exactly what different options the New Project wizard performs.
Does someone know of a document that precisely describes each option and what it produces? (Win32 App, MFC Wizard App, etc.) The help does little or nothing for me here!
I have always used a standard windows MFC app and haven't explored all of the different options.
David Leikis
Thiokol Propulsion systems
|
|
|
|
|
|
Justin, I posted your code on a BBS I read, and someone responded that it gives the expected output using gcc. So chalk it up to a VC bug, I guess.
Something else that's weird - if you try to set breakpoints on the A() and B() constructors, it will only let you break at one of them. VC will say there's no code at the line the other constructor is on. *shrug*
|
|
|
|
|
Justin, I found this MS KB article that acknowledges that this is a bug in VC. The workaround is to throw a dummy template parameter in the function, i.e.:
template<typename T> void func ( T* dummy = NULL )
|
|
|
|
|
|
Is anyone familiar with programming the Rich Ink control for a WinCE 2.11 device? If not, do you have any suggestions for implementing signature capture. Thanks.
|
|
|
|
|
I am trying to move a combo box to a new location when a specific event happens. The code I currently have is:
CComboBox* state;
// box is initialized, blah blah blah
// then, later I have
state->MoveWindow(x, y, WIDTH_INC, HEIGHT_INC, TRUE);
This causes the following error:
The instruction "0x5f436c36" referenced memory at "0xcdcdcded". The memory could not be "read".
Using the debugger to step through the program, I've discovered in the MoveWindow function, it asserts at
ASSERT(::IsWindow(m_hWnd))
Any ideas what's happening?
Thanks,
Stephanie
|
|
|
|
|
Probably you called the MoveWindow function too early. I.e. before the controls are actually created.
If I recall correctly, they are created before/after the CDialog::OnInitDialog event.
|
|
|
|
|
Here's the sequence:
The user fills in some edit fields and pushes an Allocate button. The CComboBox is created and displayed.
Everything is good at this point. I can select different items from the drop down box and everything. If
the user has selected the Allocate button more than once, there could be several of the CComboBoxes.
When the user selects a Deallocate button, the CComboBox is removed the remaining boxes need to be
moved up (they're displayed vertically). This is when MoveWindow gets called and crashes.
Does this makes sense? The CComboBox has definately been created because I can select items from it.
Do you have any other suggestions?
Thanks,
Stephanie
|
|
|
|
|
Sounds like you may be goiong in a loop somewhere to move other boxes up, so don't you think you might be trying to move the one that is already gone, possibly?
|
|
|
|
|
I thought of that also, so I put in
if (state)
AfxMessageBox("Box is good");
else
AfxMessageBox("Box is bad");
I got the Box is good message, so I think the box is still there. Is this an accurate test to see if the box
exists? Any other ideas?
Thanks again,
Stephanie
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
