Sponsored Content
The Lounge What is on Your Mind? How Much Vacation Do You Take Every Year? Post 302125722 by syndex on Friday 6th of July 2007 03:32:04 PM
Old 07-06-2007
I work for the state of pa, so I get lots of leave time Smilie.
 

2 More Discussions You Might Find Interesting

1. What is on Your Mind?

Vacation Announcements

I thought this would be a useful thread to announce vacation periods, so us regulars will be known to be on/off. If another admin thinks this is stupid, go ahead and un-pin it. (1 Reply)
Discussion started by: otheus
1 Replies

2. What is on Your Mind?

How Much Vacation Do You Take? | UNIX.com Community | Annual Vacation (YouTube)

Here is another simple YT video co-produced with our video partner. How Much Vacation Do You Take? | UNIX.com Community | Annual Vacation https://youtu.be/MSy553qS654 Background sound track is called "Caribbean Paradise" Sounds like something wisecracker would have played in one... (0 Replies)
Discussion started by: Neo
0 Replies
XtAppAddWorkProc()														XtAppAddWorkProc()

XtAppAddWorkProc - register a procedure to be called when the event loop is idle.

Synopsis
  XtWorkProcId XtAppAddWorkProc(app_context, proc, client_data)
	 XtAppContext app_context;
	 XtWorkProc proc;
	 XtPointer client_data;

Inputs
  app_context
	    Specifies the application context.

  proc	    Specifies the procedure that is to be called when the application is idle.

  client_data
	    Specifies data to be passed to proc when it is called.

Returns
  A handle of type XtWorkProcId that can be passed to XtRemoveWorkProc() to unregister the work procedure.

Description
  XtAddWorkProc()  registers  the  procedure proc and the data client_data to be called by XtAppNextEvent() or XtAppProcessEvent() when there
  are no pending input events and it would otherwise block.  Multiple work procedures can be registered, and the most recently added  one  is
  always  the  one  that  is called.  However, if a work procedure itself adds another work procedure, the newly added one has lower priority
  than the current one.

  A work procedure returns a Boolean.  If it returns True, it will automatically be unregistered and will not be called again.	If it returns
  False it will be called the next time the application is idle.  See XtWorkProc(2) for more information.

Usage
  XtAppAddWorkProc() implements a limited form of background processing.  Most applications spend most of their time waiting for input; to do
  useful work during this idle time, you can register a work procedure that will run when the application is idle.

  A work procedure must return quickly or the application will not be able to promptly respond to user events.	If a large task needs  to  be
  done	in  the background, the work procedure should periodically save its state and return False.  Work procedures should not be used to do
  frivolous work in the background.  In a multi-tasking system, an idle application should generally actually be idle, and not steal CPU time
  from other processes.

  A work procedure can be explicitly removed by calling XtRemoveWorkProc() with the XtWorkProcId returned by this function.

Structures
  The XtWorkProcId type is defined as follows:

     typedef unsigned long XtWorkProcId;

See Also
  XtAppNextEvent(1), XtAppProcessEvent(1), XtRemoveWorkProc(1),
  XtWorkProc(2).

Xt - Event Handling														XtAppAddWorkProc()
All times are GMT -4. The time now is 10:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy