[q-lang-cvs] qcalc/doc qcalc.xml,1.26,1.27

[Albert G. <ag...@us...>]

Update of /cvsroot/q-lang/qcalc/doc
In directory sc8-pr-cvs16.sourceforge.net:/tmp/cvs-serv18263/doc

Modified Files:
	qcalc.xml 
Log Message:
typo

Index: qcalc.xml
===================================================================
RCS file: /cvsroot/q-lang/qcalc/doc/qcalc.xml,v
retrieving revision 1.26
retrieving revision 1.27
diff -C2 -d -r1.26 -r1.27
*** qcalc.xml	4 Dec 2007 22:38:42 -0000	1.26
--- qcalc.xml	5 Dec 2007 00:03:43 -0000	1.27
***************
*** 507,511 ****
  
  <para>
! The <literal>task_input</literal> function equips you with a Q semaphore queue used to communicate values to the executing task in response to GUI actions inside QCalc. Usually these are either <literal>true</literal> or <literal>false</literal>, and are sent when the button state changes (<literal>true</literal> = button is switched on, i.e. the task was "started" by the user; <literal>false</literal> = button is off, the task was "stopped" or paused"). The background task can respond to these by taking some appropriate action, e.g., pause operation (or terminate altogether) if the <literal>false</literal> value is sent, or resume operation (if still active) when <literal>true</literal> is sent. Note that it is completely up to the task how it actually responds to these messages, if at all. However, it is a good idea to have the task at least empty the semaphore in regular time intervals to prevent the semaphore from being flooded with useless messages. In any case the semaphore queue will initially contain just the "startup" message (<literal>true</literal> if the task is initially started, <literal>false</literal> otherwise) when the tread is kicked off.
  </para>
  
--- 507,511 ----
  
  <para>
! The <literal>task_input</literal> function equips you with a Q semaphore queue used to communicate values to the executing task in response to GUI actions inside QCalc. Usually these are either <literal>true</literal> or <literal>false</literal>, and are sent when the button state changes (<literal>true</literal> = button is switched on, i.e. the task was "started" by the user; <literal>false</literal> = button is off, the task was "stopped" or "paused"). The background task can respond to these by taking some appropriate action, e.g., pause operation (or terminate altogether) if the <literal>false</literal> value is sent, or resume operation (if still active) when <literal>true</literal> is sent. Note that it is completely up to the task how it actually responds to these messages, if at all. However, it is a good idea to have the task at least empty the semaphore in regular time intervals to prevent the semaphore from being flooded with useless messages. In any case the semaphore queue will initially contain just the "startup" message (<literal>true</literal> if the task is initially started, <literal>false</literal> otherwise) when the tread is kicked off.
  </para>