A wxDDEClient object represents the client part of a client-server DDE (Dynamic Data Exchange) conversation.
To create a client which can communicate with a suitable server, you need to derive a class from wxDDEConnection and another from wxDDEClient. The custom wxDDEConnection class will intercept communications in a `conversation' with a server, and the custom wxDDEServer is required so that a user-overridden wxDDEClient::OnMakeConnection member can return a wxDDEConnection of the required class, when a connection is made.
This DDE-based implementation is available on Windows only, but a platform-independent, socket-based version of this API is available using wxTCPClient.
wxDDEServer, wxDDEConnection, Interprocess communications overview
Constructs a client object.
Tries to make a connection with a server specified by the host (machine name under UNIX, ignored under Windows), service name (must contain an integer port number under UNIX), and topic string. If the server allows a connection, a wxDDEConnection object will be returned. The type of wxDDEConnection returned can be altered by overriding the wxDDEClient::OnMakeConnection member to return your own derived connection object.
The type of wxDDEConnection returned from a wxDDEClient::MakeConnection call can be altered by deriving the OnMakeConnection member to return your own derived connection object. By default, a wxDDEConnection object is returned.
The advantage of deriving your own connection class is that it will enable you to intercept messages initiated by the server, such as wxDDEConnection::OnAdvise. You may also want to store application-specific data in instances of the new class.
Returns TRUEif this is a valid host name, FALSEotherwise. This always returns TRUEunder MS Windows.ymasuda 平成17年11月19日