On 2018-04-08 16:17, Hermès Bélusca-Maïto wrote:
/* Retrieve the window title of the client, if it has one */
-RtlInitEmptyUnicodeString(&WindowTitleU, NULL, 0);
+RtlInitEmptyUnicodeString(&WindowTitleU, L"", 0);
This looks like a bug. Can you explain why you think it's necessary
This change (on my own code snippet btw, see commit 5a1a35ca5a6) was necessary
because otherwise, the StringPrintf call that is done below (which would then
use a WindowTitleU.Buffer == NULL) would generate the harderror dialog title:
"(null)" (in addition to other strings being appended), inste
Well, I have not heard of anyone working on this,
and considering noone replied I would say it's not official.
On 8-6-2018 16:55, Stas'M wrote:
I've found this mirror repo on GitLab, it was created today:
https://gitlab.com/reactos/reactos
Does it belong to the ReactOS team? If not, we may hav
> Well, I have not heard of anyone working on this,
> and considering noone replied I would say it's not official.
Well this "Reactos Fond" clearly has nothing to do with us :P
--
Cheers,
Oleksandr
signature.asc
Description: This is a digitally signed message part.
__
A UNICODE_STRING with Length==0 is an empty string, the value of Buffer
is irrelevant.
If
RtlInitEmptyUnicodeString(&EmptyString, NULL, 0);
printf("%wZ", &EmptyString);
prints "(null)", then that's a bug in printf.
This special-casing with L"" is highly irregular and should be avoided.
On 2018