Vp wait: Difference between revisions

From Virtual Paradise Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
Line 8: Line 8:
   {{sdk return code row|connection_error |Waiting for data failed or there are no connections to wait for events on}}
   {{sdk return code row|connection_error |Waiting for data failed or there are no connections to wait for events on}}
|behavior=
|behavior=
* This will attempt to send all pending messages and receive all pending data within the given time limit
* This method will attempt to send all pending messages and receive all pending data within the given time limit
 
** It will wait for the full number of milliseconds if no network messages are received (or are already waiting to be processed)
 
** If one or more messages are received while waiting (or were received since the last call to vp_wait), then it will return after processing them and firing any registered event/callback handler functions.
* It will wait for the full number of milliseconds if no network messages are received for the whole duration.
** If a value of {{code|0}} milliseconds is passed, it will process any messages that have been received since the last call to vp_wait (i.e. "polling")
* If one or more messages are received while waiting, then it will return after processing them (and firing any registered event/callback handler functions).
 
 
* If a value of {{code|0}} is passed, it could still fire a number of different events


* All [[:Category:SDK events|SDK events]] and [[:Category:SDK callbacks|SDK callbacks]] are fired from this method call. Consequently, they are fired on the same thread as the caller
* All [[:Category:SDK events|SDK events]] and [[:Category:SDK callbacks|SDK callbacks]] are fired from this method call. Consequently, they are fired on the same thread as the caller
* If there is nothing to handle, it will wait until the time limit (or until one or more events or callbacks callback is fired). Else, it will return immediately after handling all pending data.
|caveats=
|caveats=
This method should never be called inside an event handler originating from a previous {{sdk method|wait}} call. The current SDK will return {{code|VP_RC_RECURSIVE_WAIT}}. For example:
This method should never be called inside an event handler originating from a previous {{sdk method|wait}} call. Note: The current SDK will simply return {{code|VP_RC_RECURSIVE_WAIT}}. For example:
<syntaxhighlight lang="c">
<syntaxhighlight lang="c">
...
...
Line 26: Line 21:
while(vp_wait(instance, 1000) == 0){}
while(vp_wait(instance, 1000) == 0){}
...
...
void event_avatar_add(VPInstance sdk)
void event_avatar_add(VPInstance instance)
{
{
     char message[300];
     char message[300];
     sprintf((char*)&message, "Hello, %s!", vp_string(sdk, VP_AVATAR_NAME));
     sprintf((char*)&message, "Hello, %s!", vp_string(sdk, VP_AVATAR_NAME));
     vp_say(sdk, (char*)&message);
     vp_say(instance, (char*)&message);
     vp_wait(instance, 1000); // Undefined behavior
     vp_wait(instance, 1000); // Undefined behavior
}
</syntaxhighlight>
The millisecond parameter should not be used for any sort of timekeeping,
<syntaxhighlight lang="c">
while (vp_wait(instance, 5000)) {
  vp_say(instance, "5 seconds have passed!"); // this is not guaranteed to occur every 5 seconds (if any message is received while waiting)
}
}
</syntaxhighlight>
</syntaxhighlight>

Latest revision as of 21:58, 20 August 2018

Method call snippet vp_wait(instance, 1000);

Pumps incoming and outgoing network traffic and fires any registered callbacks and events.

Parameters

These are the parameters that this method requires:

Parameter Usage
VPInstance
instance
Pointer to the instance this method call is intended for
int
milliseconds
Maximum amount of time to pump (in milliseconds)

Returns

This method returns a return code integer, which indicates whether the call was successful or errored for any reason:

Return code Cause
VP_RC_SUCCESS Successful call (for methods that have a registered callback, it only means the request has been sent)
VP_RC_NOT_SUPPORTED vp_wait is not supported by this instance, for example a custom vp_net_config was passed to vp_create()
VP_RC_RECURSIVE_WAIT vp_wait was called recursively on the same instance (calling it from within an event/callback handler)
VP_RC_CONNECTION_ERROR Waiting for data failed or there are no connections to wait for events on

Behavior

  • This method will attempt to send all pending messages and receive all pending data within the given time limit
    • It will wait for the full number of milliseconds if no network messages are received (or are already waiting to be processed)
    • If one or more messages are received while waiting (or were received since the last call to vp_wait), then it will return after processing them and firing any registered event/callback handler functions.
    • If a value of 0 milliseconds is passed, it will process any messages that have been received since the last call to vp_wait (i.e. "polling")
  • All SDK events and SDK callbacks are fired from this method call. Consequently, they are fired on the same thread as the caller

Caveats

This method should never be called inside an event handler originating from a previous vp_wait() call. Note: The current SDK will simply return VP_RC_RECURSIVE_WAIT. For example:

...
vp_event_set(instance, VP_EVENT_AVATAR_ADD, event_avatar_add);
while(vp_wait(instance, 1000) == 0){}
...
void event_avatar_add(VPInstance instance)
{
    char message[300];
    sprintf((char*)&message, "Hello, %s!", vp_string(sdk, VP_AVATAR_NAME));
    vp_say(instance, (char*)&message);
    vp_wait(instance, 1000); // Undefined behavior
}

The millisecond parameter should not be used for any sort of timekeeping,

while (vp_wait(instance, 5000)) {
  vp_say(instance, "5 seconds have passed!"); // this is not guaranteed to occur every 5 seconds (if any message is received while waiting)
}

Examples

This method has no usage examples; please add at least one to this page

See also