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

os::ProgressRequester Class Reference

#include <requesters.h>

Inheritance diagram for os::ProgressRequester::

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

Public Types

enum  {
  IDC_CANCEL = 1,
  IDC_SKIP
}

Public Methods

 ProgressRequester (const Rect &cFrame, const char *pzName, const char *pzTitle, bool bCanSkip)
virtual void HandleMessage (Message *pcMessage)
 Handle a message targeted at this handler. More...

void SetPathName (const char *pzString)
void SetFileName (const char *pzString)
bool DoCancel () const
bool DoSkip ()

Member Enumeration Documentation

anonymous enum
 

Enumeration values:
IDC_CANCEL  
IDC_SKIP  


Constructor & Destructor Documentation

ProgressRequester::ProgressRequester const Rect & cFrame,
const char * pzName,
const char * pzTitle,
bool bCanSkip
 


Member Function Documentation

bool ProgressRequester::DoCancel const
 

bool ProgressRequester::DoSkip
 

void ProgressRequester::HandleMessage Message * pcMessage [virtual]
 

Description:
Overload this member to dispatch messages sendt to this handler. When a looper receives a message for one of it's handlers it will call the taget handlers HandleMessage() to allow the handler to dispatch the message.

The message passed in pcMessage is also available through os::Looper::GetCurrentMessage() and os::Looper::DetachCurrentMessage() until this member returns. This is normally not very usefull for HandleMessage() itself but it can be convinient for other members called from HandleMessage() in case they need data from the message that was not passed on from HandleMessage().

The looper will be locked when this member is called. The default implementation of this member will pass the message on to the next handler if one was set with SetNextHandler().

Note:
Never do any lenthy operations in any hook members that are called from the looper thread if the looper is involved with the GUI (for example if the looper is a os::Window). The looper will not be able to dispatch messages until the hook returns so spending a long time in this members will make the GUI feel unresponsive.
Parameters:
pcMessage   The message that should be handled. This message will be deleted by the looper when HandleMessage() returns unless you detach it with os::Looper::DetachCurrentMessage(),
See also:
os::Looper::DispatchMessage(), os::Looper::DetachCurrentMessage()
Author:
Kurt Skauen (kurt@atheos.cx)

Reimplemented from os::Handler.

void ProgressRequester::SetFileName const char * pzString
 

void ProgressRequester::SetPathName const char * pzString
 


Generated at Tue Sep 11 15:27:52 2001 for AtheOS higlevel API by doxygen1.2.9.1 written by Dimitri van Heesch, © 1997-2001