Thanks for taking a closer look to it.  Yes, patch is ok.

Thanks,
Kai

2017-02-28 16:00 GMT+01:00 Guy Helmer <guy.hel...@gmail.com>:
> >From what I understand, WTSINFO was introduced in Vista/Server 2008. I have 
> >not found any evidence of changing contents of this structure since it was 
> >introduced for Vista/Server 2008.
>
> It appears to me that the structure was missing these members when the test 
> merge of Vista/7 experimental code was made back in 2010:
> commit cf6afc57179a5910621215f8f4037d406892072c
> Author: Jonathan Yong <10wa...@gmail.com>
> Date:   Tue Aug 10 08:24:16 2010 +0000
>
>     Test merge of Vista/7 experimental
>
>     git-svn-id: svn+ssh://svn.code.sf.net/p/mingw-w64/code/trunk@3198 
> 4407c894-4637-0410-b4f5-ada5f102cad1
>
> Regards,
> Guy
>
>> On Feb 28, 2017, at 8:47 AM, Kai Tietz <ktiet...@googlemail.com> wrote:
>>
>> Patch looks right.  Weren't those members present for older platforms?
>> I don't find a hint on that, but might describe why these two fields
>> are missing.
>>
>> Cheers,
>> Kai
>>
>> 2017-02-28 14:58 GMT+01:00 Guy Helmer <guy.hel...@gmail.com>:
>>> The WTSINFO structure is documented as having IncomingFrames and
>>> OutgoingFrames DWORD members after the OutgoingBytes member.
>>> ---
>>> mingw-w64-headers/include/wtsapi32.h | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>>
>>> diff --git a/mingw-w64-headers/include/wtsapi32.h 
>>> b/mingw-w64-headers/include/wtsapi32.h
>>> index fd0afba..5fe9993 100644
>>> --- a/mingw-w64-headers/include/wtsapi32.h
>>> +++ b/mingw-w64-headers/include/wtsapi32.h
>>> @@ -255,6 +255,8 @@ typedef struct _WTSINFOW {
>>>   DWORD                  SessionId;
>>>   DWORD                  IncomingBytes;
>>>   DWORD                  OutgoingBytes;
>>> +  DWORD                  IncomingFrames;
>>> +  DWORD                  OutgoingFrames;
>>>   DWORD                  IncomingCompressedBytes;
>>>   DWORD                  OutgoingCompressedBytes;
>>>   WCHAR                  WinStationName[WINSTATIONNAME_LENGTH];
>>> @@ -272,6 +274,8 @@ typedef struct _WTSINFOA {
>>>   DWORD                  SessionId;
>>>   DWORD                  IncomingBytes;
>>>   DWORD                  OutgoingBytes;
>>> +  DWORD                  IncomingFrames;
>>> +  DWORD                  OutgoingFrames;
>>>   DWORD                  IncomingCompressedBytes;
>>>   DWORD                  OutgoingCompressedBytes;
>>>   CHAR                   WinStationName[WINSTATIONNAME_LENGTH];
>>> --
>>> 2.10.2
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> Check out the vibrant tech community on one of the world's most
>>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>>> _______________________________________________
>>> Mingw-w64-public mailing list
>>> Mingw-w64-public@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> _______________________________________________
>> Mingw-w64-public mailing list
>> Mingw-w64-public@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Mingw-w64-public mailing list
> Mingw-w64-public@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to