|
I have a RichEditCtrl in a dialog box in a MFC program. While it is a simple matter to print from this, I would also like to implement a print preview. Is there any guidance available on how to do this?
|
|
|
|
|
See this[^] article is helpfuls for you,I didnt see it.
|
|
|
|
|
There is a great printing class here:
http://www.codeguru.com/cpp/w-p/printing/article.php/c2955/
I have used it along time. One problem I have, which is really
driving me crazy, is that I have a standard 8.5 x 11 sheet of paper
and cant print text past 10.5". I tried adjusting the SetBottomMargin()
function to:
pPage->SetBottomMargin(-1)
pPage->SetBottomMargin(0);
pPage->SetBottomMargin(11);
but none of them work. The text just doesnt print if it is too low
on the page.
How can print text that is close to the edge of the paper using this
class or not using this class?
Please, any response any one can give me will be greatly appreciated.
Sincerely,
Danielle Brina (an overworked graduate student)
|
|
|
|
|
hi,
i suppose that it should be changed into
double CPage::SetBottomMargin(double w)
{
int temp=m_PrtDesc.rc.bottom;
if(w > 0)
m_PrtDesc.rc.bottom=ConvertToMappedUnits(w,VERTRES);
if(w==-1)
m_PrtDesc.rc.bottom=m_PrtDesc.n_maxLength;
//m_PrtDesc.rc.right=m_PrtDesc.n_maxLength; //previous line
return ConvertToInches(temp,VERTRES);
}
and calling pPage->SetBottomMargin(-1);
|
|
|
|
|
Hello all,
I've created a special class (Class view -> right click -> add class -> MFC Class -> Add)
I've selected the base class CPropertyPage.
I'd like to use it in order to extend several pages that I have in a property sheet. Doing that I'll be able to reuse code without having to use pretranslatemessages and this kind of stuff.
The thing here is that I must be missing something:
In the header file I've changed
class CDlgPPAssEV52 : public CPropertyPage
to
class CDlgPPAssEV52 : public CPropertyPageEx
And in the implementation file I've changed
IMPLEMENT_DYNAMIC(CDlgPPAssEV52, CPropertyPage)<br />
<br />
CDlgPPAssEV52::CDlgPPAssEV52()<br />
: CPropertyPage(CDlgPPAssEV52::IDD)<br />
{<br />
}
to
IMPLEMENT_DYNAMIC(CDlgPPAssEV52, CPropertyPageEx)<br />
<br />
CDlgPPAssEV52::CDlgPPAssEV52()<br />
: CPropertyPageEx(CDlgPPAssEV52::IDD)<br />
{<br />
}
I get this error: cannot convert from '' to 'const CTAMPropertyPage'
Any idea why is this happening?
As always thank you in advance.
|
|
|
|
|
Joan Murt wrote: I get this error: cannot convert from '' to 'const CTAMPropertyPage'
On what line?
Does the CPropertyPageEx class have a constructor that takes (at least) a UINT?
Does CDlgPPAssEV52::IDD exist?
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
ooops...
It seems it was too late yesterday... the constructor did not had the UINT...
Thank you.
|
|
|
|
|
Joan Murt wrote: I get this error: cannot convert from '' to 'const CTAMPropertyPage'
What is CTAMPropertyPage?
Joan Murt wrote: Any idea why is this happening?
Based on what you've shown, no. What statement is the compiler complaining about?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
It is solved, the constructor lacked the UINT...
Sorry for the inconvenience...
|
|
|
|
|
I have dialog based app and dll which hooks WH_CBT. In the app i know which key was pressed and HWND of the app where key was pressed.
I can change keyboard layout for my own app using LoadKeyboardLayout and ActivateKeyboardLayout. But how can i change keyboard layout for another application - for the application where the key (say, i'll monitor for F9) was pressed, the one i have HWND for?
Thanks
|
|
|
|
|
As is known, Visual C++ has two character modes: ascii char (8 bits) and Unicode WCHAR (16 bits). If I use such a program to write to a .TXT file, please what is the internal format of a .TXT file, so that whatever reads it can distinguish between one 16-bit Unicode character and two adjacent ascii 8-bit characters? What are the special roles of the 8-bit control characters (ascii 0 to 31)? I know of CR LF TAB, but what do the rest do?
|
|
|
|
|
Anthony Appleyard wrote: ...what is the internal format of a .TXT file, so that whatever reads it can distinguish between one 16-bit Unicode character and two adjacent ascii 8-bit characters?
Can you use IsTextUnicode() after reading a chunk from the beginning of the file?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
|
I must make as a diploma project an "Distributed File System" with XPCOM components. I honestly don't know how to start. I followed that "Creating a C++ XPCOM component" tutorial from iosart.com/firefox/xpcom/ but I need to create XPCOM components(using VC++ 6.0) that work in a standalone program (without firefox or other platforms). What should I do ? 
Anybody who has any ideas... please help.
Thanks in advance !
|
|
|
|
|
cuesdean florin wrote: What should I do ?
Have you gone to the source[^] yet?
|
|
|
|
|
Sorry to bother you , I searched the archive but couldn't find anything that could help ...
I'm exporting a couple of entry points from a very simple Dll, and I'm doing it (so it seems
at least) in the right way , that is :
__declspec (dllexport) DWORD Function_1 (...)
{
...
}
__declspec (dllexport) DWORD Function_2 (...)
{
...
}
I'm linking the dll "explicitly", that is , I'm using the LoadLibrary() + GetProcAddress()
combination to retrieve the pointers to the entry points of the functions .
The LoadLibrary () loads correctly the dll, but the GetProcAddress() always returns NULL.
I included the dll code in a .cpp file, as I did with the calling code , so I think there
should be no name-mangling problems .
The system error code is 127, that is "the specified procedure could not be found" , as if the
export I make in the dll code is incorrect ....
Could it be a problem of calling conventions ? I tried a variety of combinations between calling
code and dll code but nothing seemed to work fine .... I know that it should be __stdcall, so I set this option both in the main and in the dll project....
Any advice ?
Thank you , a happy new year to everybody .
|
|
|
|
|
tiwal wrote: included the dll code in a .cpp file, as I did with the calling code , so I think there
should be no name-mangling problems .
I think that you'll get no name-mangling problems only with implicit linking, you probably need to surroud with extern "C" block your functions
(see http://msdn2.microsoft.com/en-us/library/ms682507.aspx[^]).
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
I've tried this option, but it does not work.
All I know is that when the C++ compiler compiles a function in a C++ file, it mangles its name, quite differently from the compiling of a C file, which doesn't do this. So if you try to export a symbol from a C file which is compled by the C++ compiler , and try to use it in a C++ file , you must tell the C++ not to mangle the call in the C++ file, and you do this by using the extern "C"
directive.
Here , I am using .cpp files in both the dll and the calling program, so there shouldn't be any of these problems ... and in effect using extern "C" , as I told you, doesn't change anything .....
|
|
|
|
|
tiwal wrote: Here , I am using .cpp files in both the dll and the calling program, so there shouldn't be any of these problems
This is wrong, because GetProcAddress does not expect a C++ mangled function.
I made a little test:
DLL header
...
#ifdef DLLTEST_EXPORTS
#define DLLTEST_API __declspec(dllexport)
#else
#define DLLTEST_API __declspec(dllimport)
#endif
#ifdef __cplusplus
extern "C"
{
#endif
DLLTEST_API int fnDLLMul(int i, int j);
#ifdef __cplusplus
};
#endif
DLL source code
...
DLLTEST_API int fnDLLMul(int i, int j)
{
return i*j;
}
Client source code
#include "stdafx.h"
#include <windows.h>
typedef int (*LPFUNMUL)(int, int);
int _tmain(int argc, _TCHAR* argv[])
{
int i=5;
int j=6;
HMODULE hLib = LoadLibrary(_T("..\\..\\DLLTest\\debug\\DllTest.Dll"));
LPFUNMUL fnMul =(LPFUNMUL) GetProcAddress(hLib, "fnDLLMul");
DWORD dwErr= GetLastError();
_tprintf(_T("%d * %d = %d"), i, j, fnMul(i,j));
getchar();
}
And it works fine (error checking left to the reader).
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
What you say is interesting : maybe GetProcAddress () has to be handled differently in a C++ environment.
By the way , I adapted my (very simple) code to your example , but it didn't work either.
I mean, I included a header file with __declspec(dllimport) and extern "C" directives in the calling code, but the error code is always the same (127).
I shouldn't need to use a header file and a dllimport directive in my case, since I'm linking my dll explicitly, and as far as I know this is only needed when you do it implicitly (that is , with a .lib for the export of symbols).
As the dll is loaded by the LoadLibrary, the system should look into its export table and check the symbol you specified in GetProcAddress () against those in that table : once it finds it, it should return the RVA associated with that symbol , so why use a header file and a dllimport statement ?
The fact instead, that GetProcAddress () couldn't be able to handle mangled names , is interesting : even if I really don't know how to work around it ....
|
|
|
|
|
tiwal wrote: By the way , I adapted my (very simple) code to your example , but it didn't work either.
I mean, I included a header file with __declspec(dllimport) and extern "C" directives in the calling code, but the error code is always the same (127).
You haven't to do this. I haven't done it. You need to use the extern "C" block when you compile your DLL using C++, because you need to export C interface (the one recognized by GetProcAddress), see (again) MSDN http://msdn2.microsoft.com/en-us/library/ms682507.aspx[^].
tiwal wrote: I shouldn't need to use a header file and a dllimport directive in my case, since I'm linking my dll explicitly, and as far as I know this is only needed when you do it implicitly (that is , with a .lib for the export of symbols).
The above is true. in fact I didn't use neither header file nor dllimport directive in my example.
tiwal wrote: he fact instead, that GetProcAddress () couldn't be able to handle mangled names , is interesting : even if I really don't know how to work around it ....
Simply GetProcAddress is designed to handle the C programming interface (WIN32 is a C API, after all), moreover, AFAIK, there is no unique standard (among compiler productors) on function name mangling.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
I've seen that you're using a dll header , which includes the exported function prototype ....
using extern "C" right before the function definition is just the same , isn't it ?
Anyway, the fact that there's no unique standard on function name mangling scares me ....
What does it mean ? that you can't use a dll in a program that's not compiled with the same environment ?
|
|
|
|
|
tiwal wrote: I've seen that you're using a dll header , which includes the exported function prototype ....
The DLL header has two purposes (a macro (un)definition makes the trick):
(1) Correctly declare the functions for exportation when compiling the DLL itself.
(2) Correctly declare the function for importation whenever you compile an application that links at load time the DLL (i.e. implicit link, via .lib file).
Since you application uses run-time (explicit) DLL link, then the header is not needed.
tiwal wrote: using extern "C" right before the function definition is just the same , isn't it ?
Using the extern "C" block when compiling (with C++) the DLL makes it exporting a C-like interface, the same kind exported by the Win32 API; run time linking such kind of interface is simpler.
tiwal wrote: Anyway, the fact that there's no unique standard on function name mangling scares me ....
What does it mean ? that you can't use a dll in a program that's not compiled with the same environment ?
Yes, there are compatibility issues, see for instance
http://blogs.msdn.com/oldnewthing/archive/2004/01/12/57833.aspx[^]
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
tiwal wrote: I'm linking the dll "explicitly", that is , I'm using the LoadLibrary() + GetProcAddress()
What is the reason you are not using the lib file for linking?
|
|
|
|
|
I could have done it implicitly, but I just want to learn how to do it explicitly, since MSDN says it can be done ...
After all ,there may be a reason for linking explicitly (that is not aborting the program in case of failure loading the dll).
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
