Commit 2f529c39 authored by Detlef Riekenberg's avatar Detlef Riekenberg Committed by Alexandre Julliard

user32: Move a comment about HLOCAL16 to user.exe.

parent e5180c10
......@@ -2094,6 +2094,17 @@ static LRESULT combo_proc16( HWND hwnd, UINT msg, WPARAM wParam, LPARAM lParam,
return wow_handlers32.combo_proc( hwnd, msg, wParam, lParam, FALSE );
}
/*********************************************************************
* edit_lock_buffer (internal)
*
* A 16 bit application might send an EM_GETHANDLE message and expect a HLOCAL16
* (16 bit SEG:OFF handler). From that moment on we have to keep using this
* 16 bit memory handler, because it is supposed to be valid at all times after
* EM_GETHANDLE.
* We create a HLOCAL16 buffer in edit_get_handle and copy the text from the
* HLOCAL buffer, when needed
*
*/
#define GWW_HANDLE16 sizeof(void*)
......
......@@ -1088,19 +1088,7 @@ static inline void text_buffer_changed(EDITSTATE *es)
}
/*********************************************************************
*
* EDIT_LockBuffer
*
* This acts as a LocalLock16(), but it locks only once. This way
* you can call it whenever you like, without unlocking.
*
* Initially the edit control allocates a HLOCAL32 buffer
* (32 bit linear memory handler). However, 16 bit application
* might send an EM_GETHANDLE message and expect a HLOCAL16 (16 bit SEG:OFF
* handler). From that moment on we have to keep using this 16 bit memory
* handler, because it is supposed to be valid at all times after EM_GETHANDLE.
* What we do is create a HLOCAL16 buffer, copy the text, and do pointer
* conversion.
* EDIT_LockBuffer
*
*/
static void EDIT_LockBuffer(EDITSTATE *es)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment