Chapter 1

This begins by creating a new window, and then setting its rectangle (relative to the screen)
to the client area rectangle passed as a parameter. From this point, I use Rect() to find
coordinates relative to the window. This rectangle is smaller than the screen area, as it
doesn't include the areas for menus, toolbars, status bars, and so on.
SetCursor(0,0) sets the board cursor to the top-left square. Set-ZoomL(1000) then
sets the initial zoom factor to one-to-one, using code that we'll look at closely in the next
section. This code calculates all the rectangles used for drawing and pointer event handling.
I then activate the app view window, so that it will respond to draw requests and input
events.
To complete setup, the view needs to know what fleet object to draw and who to tell about
input events. The controller is the object to supply this information, which it does by calling
SetController().
void CFleetView::SetController(TFleet& aFleet, MGameViewCmdHandler&
aCmdHandler)
{
iCmdHandler=&aCmdHandler;
iFleet=&aFleet;
}
This simply stores the pointers to the fleet object and the interface, implemented by the
controller that handles the player's shots at the fleet.
9.4.2 Drawing the View
Many of the CFleetView data members contain sizes that are used for drawing the view.
Shortly, I'll cover how those data members are initialized. First, though, I'll show the drawing
code. The Draw() function draws the view in three stages:
void CFleetView::Draw(const TRect&) const
{
DrawOutside();
DrawBorders();
DrawTiles();
}
DrawOutside() whites out the region outside the board, so that – as required by the
Draw() contract – the entire control is drawn.
DrawBorders() draws the top, bottom, left, and right border around the sea area:
void CFleetView::DrawBorders() const
{
DrawHorizontalBorder(iTopBorder);
DrawHorizontalBorder(iBottomBorder);
DrawVerticalBorder(iLeftBorder);
DrawVerticalBorder(iRightBorder);
}