SDK Application Structure: Difference between revisions
Jump to navigation
Jump to search
mNo edit summary |
mNo edit summary |
||
| Line 1: | Line 1: | ||
Most SDK applications have a structure similar to this: | Most SDK applications have a structure similar to this: | ||
'''Initializing''' | |||
* Call [[vp_init]] to initialize the API. | * Call [[vp_init]] to initialize the API. | ||
'''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 9: | 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''' | |||
* Call [[vp_wait]] for every created instance. | * Call [[vp_wait]] for every created instance. | ||
'''Terminating''' | |||
* Call [[vp_destroy]] for every instance. | * Call [[vp_destroy]] for every instance. | ||
Revision as of 18:05, 9 October 2007
Most SDK applications have a structure similar to this:
Initializing
- Call vp_init to initialize the API.
Creating and logging in an instance
- Call vp_create to create a new instance.
- Call vp_event_set to set events for the new instance.
- Call vp_universe_connect for the instance.
- Call vp_login for the instance.
- Call vp_enter for the instance to let it enter a world.
Event Loop
- Call vp_wait for every created instance.
Terminating
- Call vp_destroy for every instance.