Chapter 1

stream.OpenLC(aStore,aStreamId);
iEngine = new(ELeave) CGameEngine;
iEngine->InternalizeL(stream);
InternalizeL(stream);
CleanupStack::PopAndDestroy(); // stream
}
The first task is to get a GUI environment pointer. That's needed by the controller, whether
it's constructing from scratch or restoring from a document. Next, it creates a new engine
object and requests it to initialize itself from the specified stream. As you would expect,
InternalizeL()is the conventional name for functions that read data from a stream. The
controller's and engine's InternalizeL() functions are pretty well the reverse of the
ExternalizeL() functions already seen: they add little that's new, so I'll move quickly on.
9.8.3 Creating a Default Document
When the application is opened with a new file (which for UIQ is only when the application is
started for the first time), it can't restore from anything, so instead it needs a new default
document. The framework creates the actual new document file: the folder for this is devicespecific
(in the standard UIQ emulator it's C:\Documents\), while the default
document name is read from the first TBUF in the resource file ('Solo Ships' in this case).
The application class has the responsibility of setting up the application appropriately for a
default state:
CApaDocument* CGameApplication::CreateDocumentL()
{
CGameDocument* doc = new(ELeave) CGameDocument(*this);
CleanupStack::PushL(doc);
doc->ConstructL();
CleanupStack::Pop();
return doc;
}
The document second-phase constructor creates a new controller:
void CGameDocument::ConstructL()
{
iController = CGameController::NewL();
}
This uses the conventional NewL(), which constructs a default controller, rather than
restoring one from file.
9.8.4 App UI and the Document
Finally, we need to link the app UI to the document. Most importantly, the command handler
for EEikCmdExit which, in all our applications until now, has just been called Exit(), now
includes SaveL():