Main Page   Modules   Namespace List   Class Hierarchy   Alphabetical List   Compound List   File List   Namespace Members   Compound Members   File Members   Related Pages  

os_priv::DirKeeper Class Reference

Inheritance diagram for os_priv::DirKeeper:

os::Looper os::Handler List of all members.

Public Types

enum  {
  M_CHANGE_DIR = 1, M_COPY_FILES, M_MOVE_FILES, M_DELETE_FILES,
  M_RENAME_FILES, M_ENTRIES_ADDED, M_ENTRIES_REMOVED, M_ENTRIES_UPDATED
}

Public Methods

 DirKeeper (const Messenger &cTarget, const std::string &cPath)
virtual void HandleMessage (Message *pcMessage)
virtual bool Idle ()
 Hook called each time the message queue is drained. More...


Member Enumeration Documentation

anonymous enum
 

Enumeration values:
M_CHANGE_DIR  
M_COPY_FILES  
M_MOVE_FILES  
M_DELETE_FILES  
M_RENAME_FILES  
M_ENTRIES_ADDED  
M_ENTRIES_REMOVED  
M_ENTRIES_UPDATED  


Constructor & Destructor Documentation

DirKeeper::DirKeeper ( const Messenger & cTarget,
const std::string & cPath )
 


Member Function Documentation

void DirKeeper::HandleMessage ( Message * pcMessage ) [virtual]
 

Reimplemented from os::Handler.

bool DirKeeper::Idle ( ) [virtual]
 

Hook called each time the message queue is drained.

Description:
Normally the looper thread is blocked on the internal message queue waiting for messages. When one or more messages arrive it will wake up and process the messages. When all messages is processed it will first call Idle() and then go back looking for more messages. If Idle() returned false the thread will block until the next message arrive and if Idle() returned true it will just look for new messages without blocking and call Idle() again (after processing new messages if any).
Note:
The looper will not be able to process new messages until Idle() returns so it is very important to not do anything lengthy if the looper is part of for example an os::Window since that will make the application feel "unresponcive" to the user.

Returns:
The Idle() function should return true if it want to be called again imediatly after the looper has polled for new messages, or false if it don't want to be called until at least one more message has been processed.
See also:
HandleMessage(), DispatchMessage()
Author(s):
Kurt Skauen (kurt@atheos.cx)

Reimplemented from os::Looper.


The documentation for this class was generated from the following file:
Generated at Sat Apr 7 16:11:33 2001 for AtheOS higlevel API by doxygen1.2.5 written by Dimitri van Heesch, © 1997-2001