To your application, HOOPS looks like a subroutine library. Your application invokes HOOPS subroutines to insert and delete objects from the graphics database, to initiate and control rendering, and to receive input events. The order in which these operations occur is called the control flow of the application; control flow is a major topic of Chapter 4. The control flow of a typical graphics application cycles through the following steps:
This cycle repeats until the user terminates the application.
We can visualize the control flow as a repeating cycle (Figure 1.1.a). This cycle contains the main parts of HOOPS Visualize - the database and renderer, in addition to your application code, the user-input subsystem, and the end-user.
Next | Previous | Index |