case DPN_MSGID_CREATE_PLAYER:
{
HRESULT hr;
PDPNMSG_CREATE_PLAYER pCreatePlayerMsg = (PDPNMSG_CREATE_PLAYER)pMsgBuffer;
DWORD dwSize = 0;
DPN_PLAYER_INFO* pdpPlayerInfo = NULL;
hr = g_pDPServer->GetClientInfo(pCreatePlayerMsg->dpnidPlayer, pdpPlayerInfo, &dwSize, 0);
if( FAILED(hr) && hr != DPNERR_BUFFERTOOSMALL)
break;
pdpPlayerInfo = (DPN_PLAYER_INFO*) new BYTE[ dwSize ];
if( NULL == pdpPlayerInfo )
break;
ZeroMemory(pdpPlayerInfo, dwSize);
pdpPlayerInfo->dwSize = sizeof(DPN_PLAYER_INFO);
hr = g_pDPServer->GetClientInfo(pCreatePlayerMsg->dpnidPlayer, pdpPlayerInfo, &dwSize, 0);
std::cout << pdpPlayerInfo->pwszName << std::endl;
break;
}
DirectPlay - Client name and sending data to specific client
Author
I work with direct play and I have several questions about. I create a server, host a session and make possible for players to connect.
Quote:Original post by MarineiopdpPlayerInfo is a pointer to a struct which presumably contains a wide character string, so dereferencing it will just output the first character of the string.
Usestd::cout << *pdpPlayerInfo->pwszName << std::endl;
The problem (I think) is that std::cout doesn't seem to like wide character strings. Does it work if you do this?
std::cout << L"Testing" << std::endl;
If it does, what if you do:
std::cout << (LPCWSTR)pdpPlayerInfo->pwszName << std::endl;
Although if that doesn't work, I've no idea. I very rarely use STL iostreams. Another thing you could try is printf (Although it's horrible, I know):
printf("%S\n", pdpPlayerInfo->pwszName); (Note it's an upper case S for wide character strings).
Consider the following program:
When run, it outputs:
#include <iostream>int main(){ const wchar_t *foo = L"foo"; std::cout << foo << std::endl; std::wcout << foo << std::endl;}When run, it outputs:
Quote:
0x804895c
foo
Quote:Original post by rip-offAh, so std::cout can't handle wide character strings at all then? Any idea if there's a deliberate reason for that?
Consider the following program:
*** Source Snippet Removed ***
When run, it outputs:Quote:
0x804895c
foo
Quote:Original post by Evil SteveQuote:Original post by rip-offAh, so std::cout can't handle wide character strings at all then? Any idea if there's a deliberate reason for that?
Consider the following program:
*** Source Snippet Removed ***
When run, it outputs:Quote:
0x804895c
foo
AFAIK, std::cout (as a std::ostream, or std::basic_ostream<char>) has an overload for its template type pointer and std::wcout (as a std::wostream or std::basic_ostream<whcar_t>) similarly has an overload for wchar_t pointers.
Both have an overload for a void pointer, which is what is being used here.
I don't know if there is a reason for not having an object that supports both, but it certainly wouldn't surprise me if there wasn't such a reason.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
