Clinton wrote:
Does the Richedit control return an error, or clear itself when passed
EM_SETTEXTEX with lParam = NULL?
On Windows, it returns 1 and clears itself. Unless the ST_SELECTION
flag is set, in which case it returns 0, and actually replaces the text
with nothing.
My patch to wine resu
Mike McCormack wrote:
Clinton Stimpson wrote:
Oh, used internally, ok (I thought it was public and that the wine
debugger said Paf 5.2 called that lstrlenW directly).
The public version is defined in dlls/kernel/string.c, and has an
exception handler as required by Win32.
So here's anothe
Clinton Stimpson wrote:
Oh, used internally, ok (I thought it was public and that the wine
debugger said Paf 5.2 called that lstrlenW directly).
The public version is defined in dlls/kernel/string.c, and has an
exception handler as required by Win32.
So here's another patch that fixes a cr
Mike McCormack wrote:
Clinton Stimpson wrote:
The following patch will fix the crash.
MSDN documentation says "*lstrlen* assumes that /lpString/ is a
null-terminated string, or NULL"
The inline lstrlenW is used only internally by Wine code, and we want
it to crash when passed a NULL pointe
Clinton Stimpson wrote:
The following patch will fix the crash.
MSDN documentation says "*lstrlen* assumes that /lpString/ is a
null-terminated string, or NULL"
The inline lstrlenW is used only internally by Wine code, and we want it
to crash when passed a NULL pointer. In this case, you s
Hi,
On Mon, Jun 05, 2006 at 09:24:24PM -0600, Clinton Stimpson wrote:
>
> I encountered a crash when using PAF 5.2.
>
> The following patch will fix the crash.
> MSDN documentation says "*lstrlen* assumes that /lpString/ is a
> null-terminated string, or NULL"
MSDN documentation says many thin
