• <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)

            相冊

            最新隨筆

            搜索

            •  

            積分與排名

            • 積分 - 56644
            • 排名 - 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 析構時會調(diào)用 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 黃大仙 閱讀(1705) 評論(1)  編輯 收藏 引用 所屬分類: c++

            FeedBack:
            # re: MFC中 windows object 和 C++ object 2006-07-08 00:49 flyingxu
            精品久久久久久无码中文字幕| 亚洲国产天堂久久综合网站| 四虎国产精品成人免费久久| 国产精品久久久久久久人人看 | 久久青青草原亚洲av无码app| 精品久久久久香蕉网| 久久国产精品久久国产精品| 久久人人爽人人爽人人片AV东京热| 久久亚洲av无码精品浪潮| 久久天天躁夜夜躁狠狠躁2022| 久久香综合精品久久伊人| 91精品婷婷国产综合久久| 天天影视色香欲综合久久| 久久水蜜桃亚洲av无码精品麻豆 | 久久精品国产一区二区| 午夜精品久久久久成人| 日本人妻丰满熟妇久久久久久| 久久se这里只有精品| av午夜福利一片免费看久久| 亚洲欧美日韩久久精品| 曰曰摸天天摸人人看久久久| 亚洲国产另类久久久精品| 久久一本综合| 国产高潮国产高潮久久久91| 久久久久人妻精品一区| 伊人久久大香线蕉亚洲| 欧美亚洲另类久久综合婷婷| 99热都是精品久久久久久| 97久久精品无码一区二区天美| 久久亚洲AV成人无码软件| 99久久精品国产一区二区蜜芽| .精品久久久麻豆国产精品| 亚洲精品乱码久久久久久蜜桃不卡 | 久久精品一本到99热免费| 综合久久精品色| 久久精品综合网| 武侠古典久久婷婷狼人伊人| 狠狠色综合网站久久久久久久| 国产 亚洲 欧美 另类 久久 | 久久国产精品无| 久久亚洲中文字幕精品一区|