docs/latex/wx/ddeservr.tex

   1 \section{\class{wxDDEServer}}\label{wxddeserver}
   2
   3 A wxDDEServer object represents the server part of a client-server DDE
   4 (Dynamic Data Exchange) conversation (available under both Windows
   5 and UNIX).
   6
   7 \wxheading{Derived from}
   8
   9 wxDDEObject
  10
  11 \wxheading{See also}
  12
  13 \helpref{IPC overview}{ipcoverview}
  14
  15 \latexignore{\rtfignore{\wxheading{Members}}}
  16
  17 \membersection{wxDDEServer::wxDDEServer}
  18
  19 \func{}{wxDDEServer}{\void}
  20
  21 Constructs a server object.
  22
  23 \membersection{wxDDEServer::Create}
  24
  25 \func{bool}{Create}{\param{const wxString\& }{service}}
  26
  27 Registers the server using the given service name. Under UNIX, the
  28 string must contain an integer id which is used as an Internet port
  29 number. FALSE is returned if the call failed (for example, the port
  30 number is already in use).
  31
  32 \membersection{wxDDEServer::OnAcceptConnection}\label{wxddeserveronacceptconnection}
  33
  34 \func{wxDDEConnection *}{OnAcceptConnection}{\param{const wxString\& }{topic}}
  35
  36 When a client calls {\bf MakeConnection}, the server receives the
  37 message and this member is called. The application should derive a
  38 member to intercept this message and return a connection object of
  39 either the standard wxDDEConnection type, or of a user-derived type. If the
  40 topic is ``STDIO'', the application may wish to refuse the connection.
  41 Under UNIX, when a server is created the OnAcceptConnection message is
  42 always sent for standard input and output, but in the context of DDE
  43 messages it doesn't make a lot of sense.
  44
  45