Enlightenment CVS committal
Author : redalb
Project : e17
Module : libs/ecore
Dir : e17/libs/ecore
Modified Files:
Tag: SPLIT
ecore.c.in
Log Message:
more (assumed) typos..
===================================================================
RCS file: /cvsroot/enlightenment/e17/libs/ecore/Attic/ecore.c.in,v
retrieving revision 1.1.2.5
retrieving revision 1.1.2.6
diff -u -3 -r1.1.2.5 -r1.1.2.6
--- ecore.c.in 25 Feb 2003 10:32:45 -0000 1.1.2.5
+++ ecore.c.in 25 Feb 2003 17:28:39 -0000 1.1.2.6
@@ -41,12 +41,12 @@
Ecore gives you other handy primitives, such as timers to tick over for you
and call specified functions at particular times so the programmer can use
-this to do things, like animate, or ime out on connections or tasks thattake
+this to do things, like animate, or time out on connections or tasks that take
too long etc.
-Idle handlers are provided too, as well and calls on entering an idle state
+Idle handlers are provided too, as well as calls on entering an idle state
(often a very good time to update the state of the program). All events that
-enter the system are passed to specific callback functions that he program
+enter the system are passed to specific callback functions that the program
sets up to handle those events. Handling them is simple and other Ecore
modules produce more events on the queue, coming from other sources such as
file descriptors etc.
@@ -96,7 +96,7 @@
This program is very simple and does't check for errors, but it does start up
and begin a main loop waiting for events or timers to tick off. This program
-doesn't set up any, but now we can expand on this simple program a litlte
+doesn't set up any, but now we can expand on this simple program a little
more by adding some event handlers and timers.
@code
@@ -104,7 +104,7 @@
Ecore_Timer *timer1 = NULL;
Ecore_Event_Handler *handler1 = NULL;
-double start_time = 0;0;
+double start_time = 0.0;
int timer_func(void *data)
{
@@ -137,20 +137,20 @@
}
@endcode
-In the previous example, we initialize out application, get the time at which
+In the previous example, we initialize our application and get the time at which
our program has started so we can calculate an offset. We set up a timer to
tick off in 0.5 seconds, and since it returns 1, will keep ticking off every
0.5 seconds until it returns 0, or is deleted by hand. An event handler is set
up to call a function - exit_func(), whenever an event of type
-ECORE_EVENT_SIGNAL_EXIT is recieved (CTRL-C on the command line will cause
-such an event to happen). If this event occurs it telsl you what kind of
+ECORE_EVENT_SIGNAL_EXIT is received (CTRL-C on the command line will cause
+such an event to happen). If this event occurs it tells you what kind of
exit signal was recieved, and asks the main loop to quit when it is finished
by calling ecore_main_loop_quit().
The handles returned by ecore_timer_add() and ecore_event_handler_add() are
-only stored here as an example. If you don't need ot address the timer or
+only stored here as an example. If you don't need to address the timer or
event handler again you don't need to store the result, so just call the
-function, and dont assign the result to any variable.
+function, and don't assign the result to any variable.
This program looks slightly more complex than needed to do these simple
things, but in principle, programs don't get any more complex. You add more
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
enlightenment-cvs mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/enlightenment-cvs
