Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Various small fixes

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/branches/WX_2_2_BRANCH@6895 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Guillermo Rodriguez Garcia
2000-03-21 21:02:43 +00:00
parent ad269e4c7c
commit fb5e087649
2 changed files with 67 additions and 58 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/latex/wx/tsamples.tex
View File

@@ -301,8 +301,8 @@ they set up their own event handler, and then request to be notified
of {\bf wxSOCKET\_INPUT} (incoming data) or {\bf wxSOCKET\_LOST}
(connection closed at the remote end) events. In the sample, the event
handler is the same for all connections; to find out which socket the
event is addressed to, the \helpref{GetSocket}{wxsocketeventgetsocket}
function is used.
event is addressed to, the \helpref{GetSocket}{wxsocketeventgetsocket} function
is used.
Although it might take some time to get used to the event-oriented
system upon which wxSocket is built, the benefits are many. See, for
@@ -323,8 +323,8 @@ both clients and connection objects in the server set up an event handler
to catch {\bf wxSOCKET\_LOST} events, each one is immediately notified
if the other end closes the connection.
There is also an URL test which shows how to use the \helpref{wxURL}{wxurl}
class to fetch data from a given URL.
There is also an URL test which shows how to use
the \helpref{wxURL}{wxurl} class to fetch data from a given URL.
The sockets sample is work in progress. Some things to do: