Ichthyostega 6073df3554 Looper: other (better?) idea how to handle "builder dirty" automatically ... ...this means to turn Looper into a state machine. Yet it seems more feasible, since the DispatcherLoop has a nice checkpoint after each iteration through the while loop, and we'd keep that whole builder-dirty business completely confined within the Looper (with a little help of the DispatcherLoop) Let's see if the state transition logic can actually be implemented based just on such a checkpoint....?		2016-12-20 03:53:48 +01:00
..
backend	mark a solution how to create a safeguard against deadlock on session shutdown	2016-12-20 02:35:45 +01:00
common	ProcDispatcher: decide on requirements and implementation structure (#1049)	2016-12-15 20:48:35 +01:00
gui	next task: implement minimal "Session subsystem" (#318)	2016-12-12 03:45:21 +01:00
include	add two placeholder functions for now	2016-12-12 03:16:29 +01:00
lib	ProcDispatcher: decide on requirements and implementation structure (#1049)	2016-12-15 20:48:35 +01:00
lumiera	next task: implement minimal "Session subsystem" (#318)	2016-12-12 03:45:21 +01:00
plugin	Merge: change building to create modules	2008-12-20 02:15:33 +01:00
proc	Looper: other (better?) idea how to handle "builder dirty" automatically	2016-12-20 03:53:48 +01:00
tool	clean-up: sourcefile layout and spell checking	2014-10-23 23:04:35 +02:00
.gitignore
DIR_INFO	update some DIR_INFO entries	2011-04-05 00:44:30 +02:00
doxygen.dox	DOC: reorganise the Doxygen configuration and structure	2013-10-25 06:34:38 +02:00
SConscript	build/platform: make lib SigC++ available for GUI test code	2015-12-25 03:06:33 +01:00