Lines Matching refs:use
18 If you want to use sockets or derived classes such as wxFTP in a secondary thread,
58 A brief note on how to use these events:
90 To process events coming from a socket object, use the following event
192 Default constructor. Don't use it directly; instead, use
201 use \helpref{Destroy}{wxsocketbasedestroy} instead. Also, do not create
258 If you use \helpref{Error}{wxsocketbaseerror}, it will always return false.
331 absolutely necessary to use it, for example to abort an operation due to
334 socket destruction), so you don't need to use it in these cases.
400 if the last IO call failed. If this returns true, use LastError
436 use \helpref{Error}{wxsocketbaseerror} instead for that purpose.
498 \docparam{handler}{Specifies the event handler you want to use.}
526 \twocolitem{{\bf wxSOCKET\_REUSEADDR}}{Allows the use of an in-use port (wxServerSocket only)}
529 A brief overview on how to use these flags follows.
560 The {\bf wxSOCKET\_REUSEADDR} flag controls the use of the SO\_REUSEADDR standard
561 setsockopt() flag. This flag allows the socket to bind to a port that is already in use.
568 use of wxSOCKET\_REUSEADDR implies SO\_REUSEPORT in addition to SO\_REUSEADDR to be consistent
764 If you use \helpref{LastCount}{wxsocketbaselastcount}, it will always return {\it nbytes}.
766 If you use \helpref{Error}{wxsocketbaseerror}, it will always return false.
801 Note that it is recommended to use the individual Wait functions
1050 To detect this, use \helpref{WaitOnConnect}{wxsocketclientwaitonconnect},
1150 To process a socket event, use these event handler macros to direct input
1184 it possible to use the same event handler for different sockets.