Tim Mayberry 1da30faf7f Add tests that show the timing differences between the Glib/mm based timeouts ... This shows that PBD::Timer is pretty much identical in terms of timing and CPU usage as Glib TimeoutSources. They also show the differences on Windows when setting the minimum Multimedia Timer resolution using timeBeginPeriod		2015-01-01 19:04:09 +07:00
..
boost-debug
macosx
msvc
MSVCpbd
pbd
test	Add tests that show the timing differences between the Glib/mm based timeouts	2015-01-01 19:04:09 +07:00
base_ui.cc
basename.cc
boost_debug.cc
cartesian.cc
ChangeLog
cocoa_open_uri.mm
command.cc
configuration_variable.cc
controllable_descriptor.cc
controllable.cc
convert.cc
COPYING
cpus.cc
crossthread.cc
crossthread.posix.cc
crossthread.win.cc
debug_rt_alloc.c
debug.cc
enums.cc
enumwriter.cc
epa.cc
error.cc
event_loop.cc
ffs.cc
file_utils.cc
fpu.cc
gettext.h
glib_semaphore.cc
i18n.h
id.cc
libpbd.pc.in
libpbd.spec.in
locale_guard.cc
localeguard.cc
localtime_r.cc
malign.cc
md5.cc
mountpoint.cc
openuri.cc
pathexpand.cc
pbd.cc
pool.cc
property_list.cc
pthread_utils.cc
receiver.cc
resource.cc
run-tests.sh
search_path.cc
semutils.cc
shortpath.cc
signals.cc
stacktrace.cc
stateful_diff_command.cc
stateful.cc
strreplace.cc
strsplit.cc
system_exec.cc
textreceiver.cc
timer.cc
timing.cc
transmitter.cc
undo.cc
uuid.cc
whitespace.cc
windows_special_dirs.cc
wscript
xml++.cc