panda3d.core.ReMutexDirect

from panda3d.core import ReMutexDirect
class ReMutexDirect

This class implements a standard reMutex by making direct calls to the underlying implementation layer. It doesn’t perform any debugging operations.

Inheritance diagram

Inheritance diagram of ReMutexDirect

acquire() → None

Grabs the reMutex if it is available. If it is not available, blocks until it becomes available, then grabs it. In either case, the function does not return until the reMutex is held; you should then call unlock().

This method is considered const so that you can lock and unlock const reMutexes, mainly to allow thread-safe access to otherwise const data.

Also see ReMutexHolder.

acquire(current_thread: Thread) → None

This variant on acquire() accepts the current thread as a parameter, if it is already known, as an optimization.

tryAcquire() → bool

Returns immediately, with a true value indicating the mutex has been acquired, and false indicating it has not.

tryAcquire(current_thread: Thread) → bool

Returns immediately, with a true value indicating the mutex has been acquired, and false indicating it has not.

elevateLock() → None

This method increments the lock count, assuming the calling thread already holds the lock. After this call, release() will need to be called one additional time to release the lock.

This method really performs the same function as acquire(), but it offers a potential (slight) performance benefit when the calling thread knows that it already holds the lock. It is an error to call this when the calling thread does not hold the lock.

release() → None

Releases the reMutex. It is an error to call this if the reMutex was not already locked.

This method is considered const so that you can lock and unlock const reMutexes, mainly to allow thread-safe access to otherwise const data.

debugIsLocked() → bool

Returns true if the current thread has locked the ReMutex, false otherwise. This method is only intended for use in debugging, hence the method name; in the ReMutexDirect case, it always returns true, since there’s not a reliable way to determine this otherwise.

setName(name: str) → None

The mutex name is only defined when compiling in DEBUG_THREADS mode.

clearName() → None

The mutex name is only defined when compiling in DEBUG_THREADS mode.

hasName() → bool

The mutex name is only defined when compiling in DEBUG_THREADS mode.

getName() → str

The mutex name is only defined when compiling in DEBUG_THREADS mode.

output(out: ostream) → None

This method is declared virtual in MutexDebug, but non-virtual in ReMutexDirect.