Book Image

Game Programming Using Qt: Beginner's Guide

By : Lorenz Haas, Witold Wysota, Witold Wysota, Lorenz Haas
Book Image

Game Programming Using Qt: Beginner's Guide

By: Lorenz Haas, Witold Wysota, Witold Wysota, Lorenz Haas

Overview of this book

Qt is the leading cross-platform toolkit for all significant desktop, mobile, and embedded platforms and is becoming more popular by the day, especially on mobile and embedded devices. Despite its simplicity, it's a powerful tool that perfectly fits game developers’ needs. Using Qt and Qt Quick, it is easy to build fun games or shiny user interfaces. You only need to create your game once and deploy it on all major platforms like iOS, Android, and WinRT without changing a single source file. The book begins with a brief introduction to creating an application and preparing a working environment for both desktop and mobile platforms. It then dives deeper into the basics of creating graphical interfaces and Qt core concepts of data processing and display before you try creating a game. As you progress through the chapters, you’ll learn to enrich your games by implementing network connectivity and employing scripting. We then delve into Qt Quick, OpenGL, and various other tools to add game logic, design animation, add game physics, and build astonishing UI for the games. Towards the final chapters, you’ll learn to exploit mobile device features such as accelerators and sensors to build engaging user experiences. If you are planning to learn about Qt and its associated toolsets to build apps and games, this book is a must have.
Table of Contents (18 chapters)
Game Programming Using Qt
About the Authors
About the Reviewers

Time for action – sandboxed script evaluation

The next task for us is to modify our script editor so that it cleans up after the execution of each script. As was said, each script is executed in the current context of the engine, so the task of solving the problem boils down to making sure that each script executes in a separate context. Incorporate the following code in the run() method:

void MainWindow::run() {
    QString scriptSourceCode = ui->codeEditor->toPlainText();
 QScriptValue result = m_engine.evaluate
  (scriptSourceCode, windowFilePath());
    if(m_engine.hasUncaughtException()) {
        // …

Run the program and repeat the last test to see that fun no longer persists across executions.

What just happened?

When a function is called, a new execution context is pushed to the top of the stack. When the engine tries to resolve an object, it first looks for the object in the topmost...