Epok Engine

EPOK RUNTIME

epok::Tween::schedule

Method · 1 overload

Method

`wait` holds the first leg back without shortening it.

Belongs to
epok::Tween
Header
utility.hpp
Overloads
1

Declaration

Declaration
bool schedule(Fixed a,Fixed b,Fixed seconds,Ease mode,Fixed wait,TweenLoop loop,uint32_t legs)

`wait` holds the first leg back without shortening it.

ParameterTypeMeaning
aFixedValue supplied for a. Keep referenced or pointed-to data valid for the complete call.
bFixedValue supplied for b. Keep referenced or pointed-to data valid for the complete call.
secondsFixedValue supplied for seconds. Keep referenced or pointed-to data valid for the complete call.
modeEaseValue supplied for mode. Keep referenced or pointed-to data valid for the complete call.
waitFixedValue supplied for wait. Keep referenced or pointed-to data valid for the complete call.
loopTweenLoopValue supplied for loop. Keep referenced or pointed-to data valid for the complete call.
legsuint32_tValue supplied for legs. Keep referenced or pointed-to data valid for the complete call.

Returns: bool. Check the value before continuing when it represents success, availability or a resource handle.

Example

C++ example
#include "utility.hpp"

// Assume these named values have been initialized with valid data:
// Fixed a
// Fixed b
// Fixed seconds
// Ease mode
// Fixed wait
// TweenLoop loop
// uint32_t legs

epok::Tween& object = /* obtain a valid instance */;

auto result = object.schedule(a, b, seconds, mode, wait, loop, legs);

Why use it

The boolean result makes success, availability or state explicit without exceptions. The asynchronous shape lets the frame loop continue while hardware or queued work completes.

Trade-offs and warnings

Check the return value; `false` is part of normal control flow for many PSX resource operations. Captured data and buffers must remain valid until the callback or task has completed.

Declared in runtime/utility.hpp:61

Related members