GitLab

refs #384

When compiled with CAMPVIS_DEBUG, all signals carry additional information on the calling function, file and line. This is realized transparently through some macro magic when client code emits signals through the new emitSignal() method. Unfortunately, there is no way to debug-overload the operator(), hence, while this way of emitting signals remains valid, it cannot write the debug information into the signal handle.

To avoid symbol conflicts, _connection_base::emitSignal() and has_slots::emitSignal() had to be renamed to ::processSignal().

refs #384

Introducing SignalHandlingMode to signal_manager to allow forcing all signals being handled directly (needed for test-campvis) or queued.

refs #384

refs #384

* Updated sigslot::concurrent_pointer_list::insert() and sigslot::concurrent_pointer_list::push_back() to fill holes where items already have been deleted. This avoids degrading performance due to excessive fragmentation.
* Updated sigslot legal header.

* Introduced check whether signal emitting thread is the signal manager thread. In such a case signals are now emitted synchronously per default.
* Fixed sigslot shared library builds

refs #384

* Moved campvis::Runnable interface to tgt namespace (since it's needed by sigslot, which only depends on tgt)
* Introduced sigslot::signal_manager singleton class that will manage the dispatching of signals in its own thread
* Started proof-of-concept implementation of asynchroneous signals for signal0<> and signal1<>. Both classes define their own signal_handleN deriving from _signal_handle_base, which defines the signal to dispatch.

Proof-of-concept implementation seems to work so far.

refs #384

Conflicts:
	core/tools/opengljobprocessor.h
	ext/tgt/runnable.h

Conflicts:
	application/CMakeLists.txt
	core/tools/opengljobprocessor.h