no, just events, hook them, and do some action (with options : block, or not to block this windows message ).... mm ? ---------------------------- never stop coding.
You could try this
// strMessage is the text you want to send to the edit control
CString strRecvd;
m_cRichEdit.GetWindowText(strRecvd);
if(strRecvd.IsEmpty())
m_wndMonitor.SetWindowText(strMessage);
else if(!strRecvd.Right(1).CompareNoCase("\n"))
m_cRichEdit.SetWindowText(strRecvd + strMessage);
else
m_cRichEdit.SetWindowText(strRecvd +"\n"+ strMessage );
// Scroll the line down
m_cRichEdit.SetSel(-1, -1);
m_cRichEdit.SendMessage(EM_SCROLLCARET);
Hope it helps Rob
Don't worry about these first-chance exceptions - they're used as signaling mechanism by Windows itself. See KB article Q105675 for more details. Tomasz Sowinski -- http://www.shooltz.com
- It's for protection
- Protection from what? Zee Germans?
As I said: be patient - inspecting the code I've noticed You reversed the order of two code lines. The proper order is: delete pWnd; pWnd = NULL; ...no comment... ;) PS: Although delete doesn't set the pointer to NULL it is not necessarry to do that unless it's the only information about existance of an object. Greetings to all assembler dudes and especially for C64 demoscene!