Chapter 1

TEventCode is the type of window server event that is being handled; it can be one of
EEventKey, EEventKeyDown, or EEventKeyUp. For ordinary event handling, most
controls are interested in EEventKey.
If key down is relevant to your application, then the auto repeat count in the TKeyEvent
might also be of interest. It tells you how many auto repeats you have missed since you
handled the last key event.
12.1.2 Handling Pointer Events
Here's how COppFleetView handles pointer events:
void COppFleetView::HandlePointerEventL(const TPointerEvent&
}
aPointerEvent)
{
// Check whether we're interested
if(aPointerEvent.iType == TPointerEvent::EButton1Down &&
iData.iSeaArea.Contains(aPointerEvent.iPosition))
{
// Identify the tile that was hit
TInt x=(aPointerEvent.iPosition.iX-iData.iSeaArea.iTl.iX)/
iData.iTileSize;
TInt y=(aPointerEvent.iPosition.iY-iData.iSeaArea.iTl.iY)/
iData.iTileSize;
// Move cursor if necessary
TBool iCursorMoved=(x!=iCursorX || y!=iCursorY);
SetCursor(x,y);
// Hit square unless it's already known
if (iFleet.IsKnown(x,y))
else
}
{
iEikonEnv->InfoMsg(R_GAME_ALREADY_KNOWN);
if (iCursorMoved)
}
DrawTilesNow();
iData.iCmdHandler.ViewCmdHitFleet(x,y);
Like OfferKeyEventL(), HandlePointerEventL() is called on a control if the
framework thinks the pointer event ought to be handled. Generally, that means the control is
not dimmed or invisible, and it's the control with the smallest area that surrounds the
coordinates of the pointer event. Unlike OfferKeyEventL(), HandlePointerEventL()
requires the control to handle the pointer event or ignore it. The event is not offered to be