C / C++ / MFC Discussion Boards

Chinese text encoded with GB 2312 (CP936, Simplified Chinese) or Big-5 (CP950, Traditional Chinese) can be displayed in static or edit controls in MBCS apps if you adjust the font and it's properties.

For Simplified Chinese for example (m_font is CFont member of your dialog class):

LOGFONT lf;
memset(&lf, 0, sizeof(LOGFONT));
lf.lfCharSet = GB2312_CHARSET;
strcpy(lf.lfFaceName, "System");
lf.lfHeight = 17;
m_font.CreateFontIndirect(&lf);
GetDlgItem(IDC_EDIT)->SetFont(&m_font);

You'll have to run this on a Chinese system or at least set your system locale to Chinese.

The same goes for Korean and Japanese.

modified on Friday, October 23, 2009 4:00 AM

I have solved this in non-wizard generated applications by creating a virtual window in CMAinWin::CMainWin just after Create() is called using CDC and CBitmap. I use CClientDC to dreate the device context. However when I try to add this code to the wizard generated code in what I think is the same part of the code it compiles and links fine but I an assertion error at run-time. I hope this makes sense, I have been pounding my head for 3 days now. I could just settle for what I have but I would really like to use the new stuff. this is in MFC single document.

Is CClientDC the proper class to use for getting the device context for the main window?

If so, where in the new project do I create my virtual window?
I've tried every where I could think of with the same results.

Thanks for any help

Terry S.

SimpleCodr

modified on Thursday, October 22, 2009 2:05 PM

SimplCodr wrote:
I have solved this in non-wizard generated applications by creating a virtual window in CMAinWin::CMainWin just after Create() is called using CDC and CBitmap.

What? What problem? Virtual Window?!
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

If I was an expert I would not need the help. Thanks for giving it your best shot though.

If I had superpowers then I would guess what your problem was...Unfortunately I need a bit more info in order to help you in any way.
Your question isn't clear at all, for instance, what have you solved? Could you please include more context info? Could you please elaborate a bit? May I ask you politely to report the relevant code and the compiler error message?
As for my best shot, you're completely wrong: it is by no mean reserved to you.
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

I hope this clarifies a bit, if not I am too stupid to ask a question so I'll give up.

The following code works great to redraw (i think that's right) the screen anytime it is resized, minimized or covered by another window as long as the application uses the method below for creating a window.

The problem I am having is when I add the CClientDC dc(this); to a wizard generated Single or multiple document MFC application my application crashes at run-time with a debug assertion error.

How can achieve the same results in a single or multiple document MFC application created in VS2005 using the wizard?

CMainWin::CMainWin()
{
	RECT r;
	r.top = 200;
	r.left = 300;
	r.bottom = 500;
	r.right = 700;

	Create(NULL, "COM View", WS_OVERLAPPEDWINDOW, r,
			NULL, "TextMenu");

	// Load accelerator table
	if(!LoadAccelTable("TextMenu"))
		MessageBox("Cannot load accelerator table.", "Error");



	
	// Setup virtual screen for storing the view
	m_X = m_Y = 0;

	maxX = GetSystemMetrics(SM_CXSCREEN);
	maxY = GetSystemMetrics(SM_CYSCREEN);

	CClientDC dc(this);

	m_memDC.CreateCompatibleDC(&dc);
	m_bmp.CreateCompatibleBitmap(&dc, maxX, maxY - 10);
	m_memDC.SelectObject(&m_bmp);

	m_bkbrush.CreateStockObject(WHITE_BRUSH);
	m_memDC.SelectObject(&m_bkbrush);

	m_memDC.PatBlt(0, 0, maxX, maxY, PATCOPY);

	m_AnsiVarFont.CreateStockObject(ANSI_VAR_FONT);
	m_SystemFont.CreateStockObject(SYSTEM_FONT);
}

afx_msg void CMainWin::OnPaint()
{
	CPaintDC dc(this);

	dc.BitBlt(0, 0, maxX, maxY, &m_memDC, 0, 0, SRCCOPY);
}

void CMainWin::OnLButtonDblClk(UINT nFlags, CPoint point)
{
	// TODO: Add your message handler code here and/or call default
	strcpy_s(str, "Hello World");
	m_memDC.TextOutA(point.x, point.y, str, strlen(str));
	InvalidateRect(NULL);
	OnPaint();
	CFrameWnd::OnLButtonDblClk(nFlags, point);
}

Header File Stuff

class CMainWin : public CFrameWnd
{
public:

	int m_X, m_Y;
	char m_str[255];
	DCB dcb;
	CDC m_memDC;
	CBitmap m_bmp;
	CBrush m_bkbrush;
	CFont m_SystemFont, m_AnsiVarFont;
	
	HANDLE Ser1;

	CMainWin();
	
	afx_msg void OnPaint();
	
	afx_msg void OnExit();

	DECLARE_MESSAGE_MAP()
	
public:
	afx_msg int OnCreate(LPCREATESTRUCT lpCreateStruct);
public:
	afx_msg void OnLButtonDblClk(UINT nFlags, CPoint point);
private:
	CToolBar m_wndToolBar;
	CStatusBar m_wndStatusBar;
};

I hope someone help, thanks again.

Why didn't you check the Create return value?
What assertion is failing? Have you looked at call-stack debug window?
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Create(), CreateEx() are not used in the Wizard generated MFC document applications at least not as far as I can tell. That is the problem... The Wizard generated application uses a method for creating the window that I cant really nail down. Many files are created myappView, myDoc, mainFrm header files and source files not including the stdafx files. I have tried to implement the virtual window code in the Wizard generated applications and cant get beyond the CClientDC issue. If I cant get a pointer to the current views DC I cant create the virtual window for storing text etc..

How can I create a pointer to the device context of the current view in VS2005 created MFC single document application?

I am not fimiliar with the call-stack debug window I will look into that.

SimplCodr wrote:
How can I create a pointer to the device context of the current view in VS2005 created MFC single document application?

You may create it, for instance, inside the OnCreate message handler of the view. That wouldn't crash your application, anyway you probably won't get what your want.
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Is there a better method for repainting the screen when it is sized or minimized so the text is not lost? If so could you point me in the general direction.

Probably I didn't get you, but if you have to maintain the client aree content and restore it after window minimization, then you should keep all necessary data and provide the function to repaint (based on such data) inside the OnPaint method (i.e. an hardcopy of the screen content doesn't appear a good solution to me).
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Could you suggest a better method?

Also please look at my "sort of" solution attached to the next post... Thanks alot for your time.

Terry S.

I looked at the call-stack debug window while stepping through the code starting just before and and up to the CClientDC dc(this); call. At the time the "Debug assertion" error is posted the stack-call window goes blank, I can trace all the way up to the error.

Which window are you creating inside constructor? It is not a good idea to create a window before the object is fully initialized. Constructor is called when you create an object. Once object is created, then you should create a window.

CWnd* obj = new CWnd();
obj.Create(..);
obj.paint(..);

Read about CFrameWnd [^here^]

My guess is you are getting assert at CClientDC dc(this); because 'this' does not point to a valid window because your Create function never succeeded.

In wizard generated code, do you see CSingleDocTemplate object being created anywhere? may be in InitInstance? If yes, then read about that function on msdn. it's the place where view, frame etc are created. You can put a breakpoint in framewnd c'tor and before CSingleDocTemplate.

Having said all that, as far as I have understood your problem, you just need to do this:

In your wizard generated view class, create a CString variable "CString m_strText;"
in your CMyView constructor, put m_strText = "Hello";
and inside your CMyView::OnDraw, draw the text to screen.
pDC->DrawText(m_strText, ....);

Hope any of this makes sense to you,

Maybe you didn't get my phsyco babble but the previous code works perfectly as long the application is created manually using the method shown. The only portion of code that I'm trying to use is the code under "Virtual Window Stuff" the Create function in that is working fine if not I wouldn't get a window.

My problem is with App-Wizard generated MFC single document application. However I have a kind-of-solution but for what ever reason the background of the view goes black so I have to change the text color and text background. Not quite what I'm after yet.
Check out the code below it works quite well.

I think this is how it works;

A bitmsap is created to hold the content of the device context.
draw stuff is added to the bitmap in memory then pasted to the view when I call ShowIt().

I had to use a message handler or other function to create the "virtual window" (memory DC). The problem is It doesn't stick around like this I have try and keep everything in the bitmap and recreate the memory DC each time before I draw.

Source File Stuff

void Ccom_testView::OnLButtonDblClk(UINT nFlags, CPoint point)
{

	// Get the extents of the screen
	maxX = GetSystemMetrics(SM_CXSCREEN);
	maxY = GetSystemMetrics(SM_CYSCREEN);

	CClientDC dc(this);
	memDC.CreateCompatibleDC(&dc);

	if (m_bmp.m_hObject == NULL)
		m_bmp.CreateCompatibleBitmap(&dc, maxX, maxY);

	memDC.SelectObject(&m_bmp);


	// This does not do what it should. Expect a white background.
	// Program Still starts with a black background
	bkBrush.CreateStockObject(WHITE_BRUSH);
	memDC.SelectObject(&bkBrush);

	CBitmap* pOldBitmap = memDC.SelectObject(&m_bmp);
	CBrush* pOldbkBrush = memDC.SelectObject(&bkBrush);
	
	// Had to set text color manually
	memDC.SetTextColor(RGB(0, 200, 100));
	memDC.SetBkColor(RGB(0,0,0));	

	wsprintf(str, "Hello World");
	memDC.TextOutA(point.x, point.y, str, strlen(str));

	memDC.SelectObject(pOldbkBrush);

	memDC.SelectObject(pOldBitmap);
	memDC.DeleteDC();

	ShowIt();

	CView::OnLButtonDblClk(nFlags, point);
}

void Ccom_testView::OnPaint()
{
	CPaintDC dc(this); // device context for painting
	// TODO: Add your message handler code here
	ShowIt();
	
	//	dc.BitBlt(0, 0, maxX, maxY, &memDC, 0, 0, SRCCOPY);
	// Do not call CView::OnPaint() for painting messages
}

bool Ccom_testView::ShowIt(void)
{
//	CDC memDC;
	CClientDC dc(this);
	CBitmap* pbmOld = NULL;

	memDC.CreateCompatibleDC(&dc);
	pbmOld = memDC.SelectObject(&m_bmp);
	
	dc.BitBlt(0, 0, maxX, maxY, &memDC, 0, 0, SRCCOPY);

	memDC.SelectObject(pbmOld);
	memDC.DeleteDC();
	
	return false;
}


Header File Stuff

class Ccom_testView : public CView
{
public:
	CDC memDC;
	CBrush bkBrush;
	CBitmap m_bmp;
	CFont m_SystemFont, m_AnsiVarFont;

protected: // create from serialization only
	Ccom_testView();
	DECLARE_DYNCREATE(Ccom_testView)

// Attributes
public:
	Ccom_testDoc* GetDocument() const;

// Operations
public:

// Overrides
public:
	virtual void OnDraw(CDC* pDC);  // overridden to draw this view
	virtual BOOL PreCreateWindow(CREATESTRUCT& cs);
protected:
	virtual BOOL OnPreparePrinting(CPrintInfo* pInfo);
	virtual void OnBeginPrinting(CDC* pDC, CPrintInfo* pInfo);
	virtual void OnEndPrinting(CDC* pDC, CPrintInfo* pInfo);

// Implementation
public:
	virtual ~Ccom_testView();
#ifdef _DEBUG
	virtual void AssertValid() const;
	virtual void Dump(CDumpContext& dc) const;
#endif

protected:

// Generated message map functions
protected:
	DECLARE_MESSAGE_MAP()
public:
	afx_msg void OnLButtonDblClk(UINT nFlags, CPoint point);
public:
	afx_msg void OnPaint();
public:
	bool ShowIt(void);
};

Comments or suggestions would be great. Even better yet a better way to do it.

Thank you for your help.

I am not an expert myself but you can try few changes -

Create a new bitmap everytime you create a new memdc.

bool Ccom_testView::ShowIt(void)
{
//	CDC memDC;

	CClientDC dc(this);
	CBitmap* pbmOld = NULL;

	memDC.CreateCompatibleDC(&dc);
CBitmap memBmp;
memBmp.CreateCompatibleBitmap(&dc);

	pbmOld = memDC.SelectObject(&membmp);
	
	dc.BitBlt(0, 0, maxX, maxY, &memDC, 0, 0, SRCCOPY);

	memDC.SelectObject(pbmOld);
memBmp.DeleteObject();
	memDC.DeleteDC();
	
	return false;
}

Idont undersatnd your code in LButtonDblClk..
try to do all text out stuff etc into memDC and then simply BitBlt memDC onto CPaintDC.

All painting stuff should go inside OnPaint..

Basically the LButtonDblClk function is using TextOut to put "Hello World" on the screen at the cursors position. The intention is to have the output accumulate on the screen and remain on the screen when resized, minimized or covered by another window etc...

I tried recreating the bitmap each time by changing the conditional statement at the beginning of LButtonDblClk if(!= NULL)delete the bitmap and just have the bitmap created each time the problem with that is the output does not accumulate on the screen.

I will try what you have here to see if my results can improve. Again this code is working, it just paints the background black and I am having trouble figuring out why that is, I have been messing with this same project for a while, maybe I'll try generating a new one and see what happens.

I am puzzled why this is so difficult to solve, although I have not written alot of code I have been doing it for a long time and the programmer has always had to take care of refreshing the screen and keeping the output(text, graphics etc..) on there theirself, at least I have. So what does a novice have to do to get the information or at least a clue to the solution. This cannot be stumping the programming gurus here in this forum, no way.

Thanks again
Terry S.

So what you intend to do is (correct if I'm wrong):
When user double clicks the left mouse button, draw some graphics and make it permanent.

If I guessed well then you have to:

Properly erase the background (see [^]).
Make your painting function (i.e. ShowIt() ) accepting as argument, a CPaintDC instead of creating its own device context.
Never call directly your paint function (or other drawing code, use instead InvalidateRect and UpdateWindow to force the painting happen).
inside the button handler just set a flag (a member variable of the class) and use it to conditionally call your painting function inside OnPaint

For instance:

void Ccom_testView::OnLButtonDblClk(UINT nFlags, CPoint point)
{
  // don't put drawing stuff here
  m_showit=true;
  // the following calls force the window re-paint
  InvalidateRect(NULL);
  UpdateWindow();
  //...
}

void Ccom_testView::OnPaint()
{	
  CPaintDC dc(this); // device context for painting
  if (m_showit) 
    ShowIt(dc);
  //...
}
void Ccom_testView::ShowIt(CPaintDC & dc)
{
  // use the passed dc for drawing
}

Hope it eventually makes sense.

Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Actually this makes alot of of sense, I have a better time making sense of things than I do communicating them in a way that makes sense, if that makes sense Smile | :)

.

Seriously I think this is going to work for me once I get it implemented properly. I have always been week at passing perameters and therefore I avoid it and never think about the possibilities. I have alot to learn but I'm not going to give up.

Thank you very much for your help, I have learned a great deal just in the communications, that's asside from the code information.

Terry S.

I thought I had it...

Here is what I got, it all compiles and runs great but I never see anything show up on the window.

What did I do wrong or not do?

void CComViewView::OnDraw(CDC* /*pDC*/)
{
	CComViewDoc* pDoc = GetDocument();
	ASSERT_VALID(pDoc);
	if (!pDoc)
		return;

	// TODO: add draw code for native data here
	CPaintDC dc(this);

	if(m_show)
		ShowIt(dc);
}

void CComViewView::OnLButtonDblClk(UINT nFlags, CPoint point)
{
	// TODO: Add your message handler code here and/or call default
	pos = point;
	m_show = true;
	m_userIn = true;

	InvalidateRect(NULL);
	UpdateWindow();

	CView::OnLButtonDblClk(nFlags, point);
}

void CComViewView::ShowIt(CPaintDC & dc)
{
	if(!m_userIn)return;

	maxX = GetSystemMetrics(SM_CXSCREEN);
	maxY = GetSystemMetrics(SM_CYSCREEN);

	CDC memDC;
	CBitmap m_bmp;
	
	memDC.CreateCompatibleDC(&dc);
	m_bmp.CreateCompatibleBitmap(&dc, maxX, maxY);
	memDC.SelectObject(&m_bmp);

	memDC.SetTextColor(RGB(0, 200, 100));
	memDC.SetBkColor(RGB(0,0,0));	

	wsprintf(str, "Hello World");
	memDC.TextOutA(pos.x, pos.y, str, strlen(str));

	memDC.BitBlt(0, 0, maxX, maxY, &memDC, 0, 0, SRCCOPY);
	UpdateWindow();

	// Set this false to keep from executing draw code
	// on window update
	m_userIn = false;
}

SimplCodr wrote:

void CComViewView::OnDraw(CDC* /*pDC*/)
{
CComViewDoc* pDoc = GetDocument();
ASSERT_VALID(pDoc);
if (!pDoc)
return;

// TODO: add draw code for native data here
CPaintDC dc(this);

if(m_show)
ShowIt(dc);
}

You don't need to create a new dc, change to (note I uncommented the pDC argument)

void CComViewView::OnDraw(CDC* pDC)
{
CComViewDoc* pDoc = GetDocument();
ASSERT_VALID(pDoc);
if (!pDoc)
return;

if(m_show)
ShowIt(*pDC);
}

SimplCodr wrote:
memDC.BitBlt(0, 0, maxX, maxY, &memDC, 0, 0, SRCCOPY);

This is the mistake, change to

dc.BitBlt(0, 0, maxX, maxY, &memDC, 0, 0, SRCCOPY);

You've to work on the background, there are still some flaws, but it is much better now.
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Excellent, I think I have everything I will need I just need to plug away at it for a while before I come crying for more help. Thanks a bunch. Big Grin | :-D

You are welcome.
Smile | :)

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.

This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke

[My articles]

Try [^vc++ in 21 days^] It will give you very good idea of mfc in 2 or 3 days. it's the shortest and most effective way known to me to learn about mfc. it may be a bit dated but the concepts are same and you don't need to spend big bucks to purchase it from nearby second hand bookshop or if you are really smart, you can find an ebook floating around somewhere in this cyberspace. Smile | :)

(i know no one likes to spend money on buying fat and boring technical books)

.. and i hope your problem is solved by now.

I like to learn and books are good way to start... I accually own the predecessor to that book "C++ in 21 days" which I found to be quite good. I also found "MFC From the Ground Up" which is a great book if you are compiling using Visual C++ 6.0, it seems like things are done non-stansard though, you have to change alot things around to get them to compile and run from the VS2005 that I have now. It's really a good thing Microsoft made it difficult to go back to old version of compiler, cause I would have and not learned what I have. Man and I'll tell you from A novices perspective that upgrade has caused me more pain than I ever imagined I could get from writting my simple code. I think there is a new book out something like MFC from the ground up for VS2005, if that's the case I would really like to get a copy of that.

It's people like you and Pallini that make me come here when I need help. You folks are awesome keep up the good work and thank you.

Terry S.