SDK Application Structure: Difference between revisions

From Virtual Paradise Wiki
Jump to navigation Jump to search
mNo edit summary
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
Most SDK applications have a structure similar to this:
Most SDK applications have a structure similar to this:
== Initializing ==
 
'''Initializing'''
* Call [[vp_init]] to initialize the API.
* Call [[vp_init]] to initialize the API.
== Creating and logging in an instance ==
'''Creating and logging in an instance'''
* Call [[vp_create]] to create a new instance.
* Call [[vp_create]] to create a new instance.
* Call [[vp_event_set]] to set events for the new instance.
* Call [[vp_event_set]] to set events for the new instance.
Line 8: Line 9:
* Call [[vp_login]] for the instance.
* Call [[vp_login]] for the instance.
* Call [[vp_enter]] for the instance to let it enter a world.
* Call [[vp_enter]] for the instance to let it enter a world.
== Event Loop ==
'''Event Loop'''
* Call [[vp_wait]] for every created instance.
* Call [[vp_wait]] for every created instance.
== Terminating ==
'''Terminating'''
* Call [[vp_destroy]] for every instance.
* Call [[vp_destroy]] for every instance.
[[Category: SDK]]

Latest revision as of 20:02, 29 July 2012

Most SDK applications have a structure similar to this:

Initializing

  • Call vp_init to initialize the API.

Creating and logging in an instance

Event Loop

  • Call vp_wait for every created instance.

Terminating