Ichthyostega 9b8fae1a9b (re)consider the problem how to deal with mandatory/optional object fields ... this is a tricky problem and a tough decision. After quite some pondering I choose to enforce mandatory fields through the ctor, and not to allow myself cheating my way around it		2016-12-03 19:37:52 +01:00
..
backend	wrap-up(#985): resolve various leftovers	2016-01-10 11:21:34 +01:00
common	Ticket #1034 : leave note at dlclose() call	2016-10-28 16:54:02 +02:00
gui	(re)consider the problem how to deal with mandatory/optional object fields	2016-12-03 19:37:52 +01:00
include	allow for trace-logging the processed diff-tokens	2015-11-01 03:54:43 +01:00
lib	define creation and control structure of TimelineWidget	2016-12-03 05:42:34 +01:00
lumiera	release prep: remove defunct autotools buildsystem	2013-10-29 03:47:50 +01:00
plugin
proc	define creation and control structure of TimelineWidget	2016-12-03 05:42:34 +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