Class CPageBuffer

class CPageBuffer : public CActive;

Description

Derivation

• CBase - Base class for all classes to be instantiated on the heap

• CActive - The core class of the active object abstraction

• CPageBuffer - (No abstract)

Members

Defined in CPageBuffer:
AddBytesL(), CloseWriteStream(), CreateWriteStreamL(), DoCancel(), NewL(), NewL(), RunL(), StartFlush(), ~CPageBuffer()

Inherited from CActive:
Cancel(), Deque(), EPriorityHigh, EPriorityIdle, EPriorityLow, EPriorityStandard, EPriorityUserInput, Extension_(), IsActive(), IsAdded(), Priority(), RunError(), SetActive(), SetPriority(), TPriority, iStatus

Inherited from CBase:
Delete(), operator new()

static IMPORT_C CPageBuffer *NewL(CPrinterPort *aPrinterPort);

Description

Parameters

CPrinterPort *aPrinterPort

Return value

CPageBuffer *

static IMPORT_C CPageBuffer *NewL(CPrinterPort *aPrinterPort, TInt aGranularity);

Description

Parameters

CPrinterPort *aPrinterPort TInt aGranularity

Return value

CPageBuffer *

IMPORT_C ~CPageBuffer();

Description

IMPORT_C void StartFlush(TRequestStatus &aRequestStatus);

Description

Parameters

TRequestStatus &aRequestStatus

IMPORT_C void AddBytesL(const TDesC8 &aDes);

Description

Parameters

const TDesC8 &aDes

IMPORT_C RWriteStream &CreateWriteStreamL();

Description

Return value

RWriteStream &

IMPORT_C void CloseWriteStream();

Description

virtual void DoCancel();

Description

Implements cancellation of an outstanding request.

This function is called as part of the active object's Cancel().

It must call the appropriate cancel function offered by the active object's asynchronous service provider. The asynchronous service provider's cancel is expected to act immediately.

DoCancel() must not wait for event completion; this is handled by Cancel().

virtual void RunL();

Description

Handles an active object's request completion event.

A derived class must provide an implementation to handle the completed request. If appropriate, it may issue another request.

The function is called by the active scheduler when a request completion event occurs, i.e. after the active scheduler's WaitForAnyRequest() function completes.

Before calling this active object's RunL() function, the active scheduler has:

1. decided that this is the highest priority active object with a completed request

2. marked this active object's request as complete (i.e. the request is no longer outstanding)

RunL() runs under a trap harness in the active scheduler. If it leaves, then the active scheduler calls RunError() to handle the leave.

Note that once the active scheduler's Start() function has been called, all user code is run under one of the program's active object's RunL() or RunError() functions.