• <ins id="pjuwb"></ins>
    <blockquote id="pjuwb"><pre id="pjuwb"></pre></blockquote>
    <noscript id="pjuwb"></noscript>
          <sup id="pjuwb"><pre id="pjuwb"></pre></sup>
            <dd id="pjuwb"></dd>
            <abbr id="pjuwb"></abbr>
            隨筆 - 25  文章 - 29  trackbacks - 0
            <2006年7月>
            2526272829301
            2345678
            9101112131415
            16171819202122
            23242526272829
            303112345

            常用鏈接

            留言簿(4)

            隨筆分類(22)

            隨筆檔案(25)

            文章分類(2)

            文章檔案(2)

            相冊

            最新隨筆

            搜索

            •  

            積分與排名

            • 積分 - 56615
            • 排名 - 405

            最新評論

            閱讀排行榜

            評論排行榜

            The Problem

            Windows objects are normally represented by HANDLEs. The MFC classes wrap Windows object handles with C++ objects. The handle wrapping functions of the MFC class library provide a way to find the C++ object that is wrapping the Windows object with a particular handle. There are times when a Windows object does not have a C++ wrapper object, however, and at these times a temporary object is created to act as the C++ wrapper.

            mfc 映射的 windows object ---->c++ wrapper
            以下使用 mfc 的函數(shù) 如:fromhandle, getdlgitem,都會返回temporary 和 pemanent? c++ wrapper object
            ?注意:
            ???? 零時的 對象 會被在空閑時(OnIdle()函數(shù))被刪除,不能存下在下次消息處理中 使用
            The default OnIdle processing in CWinThread automatically calls DeleteTempMap for each class that supports temporary handle maps
            ////////////////////////////////////////////////////////////
            The Windows objects that use handle maps are:

            • HWND (CWnd and CWnd-derived classes)
            • HDC (CDC and CDC-derived classes)
            • HMENU (CMenu)
            • HPEN (CGdiObject)
            • HBRUSH (CGdiObject)
            • HFONT (CGdiObject)
            • HBITMAP (CGdiObject)
            • HPALETTE (CGdiObject)
            • HRGN (CGdiObject)
            • HIMAGELIST (CImageList)
            • SOCKET (CSocket)

            ///////////////////////////////////////////////

            Given a handle to any of these objects, you can find the MFC object that wraps the handle by calling the static member function FromHandle. For example, given an HWND called hWnd:

            CWnd::FromHandle(hWnd)

            will return a pointer to the CWnd that wraps the hWnd. If that hWnd does not have a specific wrapper object, then a temporary CWnd is created to wrap the hWnd. This makes it possible to get a valid C++ object from any handle.

            Once you have a wrapper object, you can get to its handle through a public member variable. In the case of a CWnd, m_hWnd contains the HWND for that object.

            Attaching Handles to MFC Objects

            Given a newly created handle-wrapper object and a handle to a Windows object, you can associate the two by calling Attach. For example:

            CWnd myWnd;
            myWnd.Attach(hWnd);
            ////mywnd 析構時會調用 destroywindow ,連同 hwnd 一起銷毀




            This makes an entry in the permanent map associating myWnd and hWnd.
            Calling CWnd::FromHandle(hWnd) will now return a pointer to myWnd.
            When myWnd is deleted, the destructor will automatically destroy the hWnd by calling the Windows DestroyWindow function. If this is not desired, the hWnd must be detached from myWnd before the myWnd object is destroyed (normally when leaving the scope at which myWnd was defined). The Detach member function does this.

            myWnd.Detach();

            More About Temporary Objects

            Temporary objects are created whenever FromHandle is given a handle that does not already have a wrapper object. These temporary objects are detached from their handle and deleted by the DeleteTempMap functions. The default OnIdle processing in CWinThread automatically calls DeleteTempMap for each class that supports temporary handle maps. This means that you cannot assume a pointer to a temporary object will be valid past the point of exit from the function where the pointer was obtained, as the temporary object will be deleted during the Windows message-loop idle time.

            很重要:
            在多線程中傳遞 c++ wrapper object 是無效的(無論是 temporary 還是 permanent)
            只能傳遞 windows handle, 換句話就是說, 線程 只能 訪問 自己創(chuàng)建的c++ wrapper object

            Wrapper Objects and Multiple Threads

            Both temporary and permanent objects are maintained on a per-thread basis. That is, one thread cannot access another threads C++ wrapper objects, regardless of whether it is temporary or permanent. As stated above, temporary objects are deleted when the thread which that temporary object belongs enters OnIdle.

            To pass these objects from one thread to another, always send them as their native HANDLE type. Passing a C++ wrapper object from one thread to another will often result in unexpected results.

            ????

            posted on 2006-06-30 11:33 黃大仙 閱讀(1702) 評論(1)  編輯 收藏 引用 所屬分類: c++

            FeedBack:
            # re: MFC中 windows object 和 C++ object 2006-07-08 00:49 flyingxu
            香港aa三级久久三级老师2021国产三级精品三级在 | 国产成人精品综合久久久久 | 久久性精品| 97视频久久久| 一本大道加勒比久久综合| 国内精品久久国产大陆| 久久天天躁狠狠躁夜夜av浪潮| 国产精品免费久久久久电影网| 人妻无码久久精品| 亚洲人成精品久久久久| 亚洲综合久久综合激情久久| 中文字幕无码久久久| 精品亚洲综合久久中文字幕| 久久亚洲电影| 久久久久四虎国产精品| 囯产精品久久久久久久久蜜桃 | 一级女性全黄久久生活片免费| 99久久国语露脸精品国产| 亚洲另类欧美综合久久图片区| 99久久人妻无码精品系列| 欧美精品国产综合久久| 欧美久久久久久精选9999| 狠狠干狠狠久久| 久久精品中文无码资源站| 乱亲女H秽乱长久久久| 久久久久久久人妻无码中文字幕爆| 亚洲精品99久久久久中文字幕 | 久久一区二区三区99| 久久九九免费高清视频| 热久久国产欧美一区二区精品 | 久久精品a亚洲国产v高清不卡| 亚洲综合精品香蕉久久网| 久久久久亚洲AV片无码下载蜜桃| 理论片午午伦夜理片久久| 久久中文字幕人妻丝袜| 亚洲国产另类久久久精品 | 伊人 久久 精品| 久久国产精品99精品国产987| 99久久无码一区人妻| 99精品久久精品一区二区| 亚洲欧美日韩精品久久|