Jolt Physics in this process: whether its native library is in the build, and its one job system.
Call start before making a world (jj_world_create). The first call
decides the job system's size; later calls return the first answer.
In a debug build the first start of an isolate also destroys every world a previous isolate left behind: after a hot restart the old Dart objects are gone but the native worlds are not. Use Jolt from one isolate per process.
Properties
- hashCode → int
-
The hash code for this object.
no setterinherited
- runtimeType → Type
-
A representation of the runtime type of the object.
no setterinherited
Methods
-
noSuchMethod(
Invocation invocation) → dynamic -
Invoked when a nonexistent method or property is accessed.
inherited
-
toString(
) → String -
A string representation of this object.
inherited
Operators
-
operator ==(
Object other) → bool -
The equality operator.
inherited
Static Properties
- hasDebugRenderer → bool
-
Whether the library has Jolt's debug renderer (the dev flavour).
no setter
- isAvailable → bool
-
Whether start succeeded (starting Jolt if it has not been).
no setter
- liveWorlds → int
-
How many native worlds are alive in this process (for leak checks).
no setter
- version → String?
-
Jolt's version,
major.minor.patch; null when it is not available.no setter
Static Methods
-
destroyAll(
) → void - Destroys every native world in this process, whoever made it.
-
start(
{int workerThreads = -1}) → String? -
Starts Jolt with a job system of
workerThreadsthreads (below 0: cores minus one). Null when Jolt is ready, otherwise why it is not — most often that the app did not ask for the library to be built.