C / C++ / MFC

Re: Clipboard & Lines :: MFC

17-Sep-02 21:24

That sounds like a good plan to me!

The data must be in a registered clipboard format, and CF_TEXT (or CF_UNICODETEXT) is probably the one to ask for. This gives you the raw character (or wide character data), and it will have embedded newline or carriage-return/newline pairs as they were placed in by the source of the cut or copy.

You could use a CString and the Find() member, or if not, then something like strchr, wcschr or for portability, _tcschr would help you find the line breaks. If you are happy to modify a copy of the data, strtok (_tcstok) would be easy enough.

Steve S
[This signature space for rent]

includeh1017-Sep-02 21:23

Re: Clipboard & Lines :: MFC

17-Sep-02 21:23

the process is
1. check clipboard format (text in ur case)
2. get the data
3. the data should be: line0\r\nline1\r\nline2 if 3 lines for nodepad

includeh10

valikac18-Sep-02 4:37

valikac

18-Sep-02 4:37

Okay. Thanks everyone.

Kuphryn

what is wrong with my thread? help

includeh1017-Sep-02 21:11

17-Sep-02 21:11

in CDocument sub-class, i create a thread to access a buffer, at the CDocument closing time, sometimes a run-time happens. i don't know why.

coding as this:

class MyDoc: public CDocument
{
..................
//they are init as null in constructor
HANDLE hThread;
BOOL bLoop;
DWORD dwThreadID;
char*pBuf;
};

MyDoc:OnOpenDocument(...)
{
pBuf=new char [50000];
hThreat=CreateThread((LPSECURITY_ATTRIBUTES)0,0,
(LPTHREAD_START_ROUTINE)Proc_Thread,
this,0,&dwThreadID);
.........................
}

void MyDoc::OnCloseDocument()
{
bLoop=0;
if(hThread)CloseHandle(hThread);
if(dwThreadID)::PostThreadMessage(dwThreadID,WM_QUIT,0,0);
::WaitForSingleObject(hThread,(UINT)(-1));
delete []pBuf;
................................
}

int WINAPI Proc_Thread(void*pVoid)
{
MyDoc*p=(MyDoc*)pVoid;
char*pBuf=p->pBuf;
while(p->bLoop)
{
//access pBuf
}
return 1;
}

note: the only problem is at closing time.
is something wrong with the coding?

thx

includeh10

valikac17-Sep-02 21:17

valikac

17-Sep-02 21:17

Post a message at the end of Proc_Thread() informing the primary thread that the worker thread has closed. That will help make synchronization smoother.

Kuphryn

Steve S17-Sep-02 21:27

17-Sep-02 21:27

Another alternative would be to WaitForSingleEvent on the thread handle in your UI thread, to guarantee that the worker thread has completed.

When the "primary" thread terminates, this usually calls ExitProcess at some stage, which kind of tears things from under the feet of other threads...

Steve S
[This signature space for rent]

includeh1017-Sep-02 21:27

17-Sep-02 21:27

but i can't find the function WaitForSingleEvent?
thx

Steve S17-Sep-02 22:02

17-Sep-02 22:02

Ah. That's because I meant to type WaitForSingleObject instead.
Frown | :-(

Sorry about that, it's early in the morning here, and I didn't get much sleep.

Steve S
[This signature space available for rent]

includeh1017-Sep-02 21:44

17-Sep-02 21:44

thx, it is 100% new for me, but what does post a message mean?
post what messge? inside or outside loop?
please give me more details.

thx

includeh10

valikac18-Sep-02 4:35

valikac

18-Sep-02 4:35

Posting a message at the end of a thread will update your primary thread on the status of the worker thread. For example, the message could trigger the primary thread to display the updated data. Furthermore, you should always post a message so that the primary thread can call closehandle() to ensure the thread is closed.

Kuphryn

Re: Help: ClassWizard error!

Stephane Rodriguez.17-Sep-02 22:09

Stephane Rodriguez.

17-Sep-02 22:09

returning from your Proc_Thread procedure automatically destroys the thread, without needing to send it any other message. A normal Proc_Thread has an event/message loop of the form :

// Wait for the signal to create a component.
BOOL bContinue = TRUE;

while ( bContinue )
{
    switch( ::WaitForSingleObject( m_hComponentReadyEvent, m_WaitTime) )
    {
        // Update the surface becoz now it's ready
        case WAIT_OBJECT_0:
            if ( !m_bShouldStopNow )
            {
                //processPublishDirectory();
            }
            break ;
        // Process Windows messages.
        case (WAIT_OBJECT_0 + 1):
            MSG msg ;
            while(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE))
            {
                if (msg.message == WM_QUIT)
                {
                    bContinue = FALSE ;
                    break ;
                }
                                    TranslateMessage(&msg);
                DispatchMessage(&msg) ;
            }
            break ;
        // Do background processing.
        case WAIT_TIMEOUT:
            if (m_bShouldStopNow)
                bContinue=FALSE;
            break ;

        default:
            break;
    }
}

MS quote (http://www.microsoft.com/ddk) : As of September 30, 2002, the Microsoft® Windows® 2000 DDK, the Microsoft Windows 98 DDK, and the Microsoft Windows NT® 4.0 DDK will no longer be available for purchase or download on this site.

Help: ClassWizard error!

Daniel Strigl17-Sep-02 20:38

Daniel Strigl

17-Sep-02 20:38

I have a problem...
When I am add some 'defines' in the 'resource.h' file, like

#define ID_BAND 110
...

and after that I try to open the class wizard, the class wizard put an error on the screen: "Parsing error: afx Message... input string: "LPTSTR MakeString(UINT..."

I searched and found out, that the following section in the 'MainFm.h' file producing the error:

// Generated message map functions
protected:
  //{{AFX_MSG(CMainFrame)
  afx_msg int OnCreate(LPCREATESTRUCT lpCreateStruct);
    LPTSTR MakeString(UINT stringID);
    LPTSTR m_ToolTipsTable[NUM_TOOL_TIPS];
	// NOTE - the ClassWizard will add and remove member functions here.
	//    DO NOT EDIT what you see in these blocks of generated code!
  //}}AFX_MSG
  DECLARE_MESSAGE_MAP()

Can anyone help me??? (I use embedded Visual C++ 3.0)

--
Nice greets, Daniel.

Steve S17-Sep-02 21:18