Daniel Zaoui 4effc37ab0 Support reference timestamp ... An issue due to timing happens when applying scenarios on applications. The first event is directly treated, even if the recorder waited a few seconds without any action. The reason is that Exactness saves in the .rec file a timestamp that is the uptime value, i.e an absolute value. A better choice would have been to save the number of ms relative to the launch of the application. Because of this, Exactness doesnt have any way to know when the first event has to be treated and consumes it whenever possible, i.e at the beginning. This patch adds to the recording file a timestamp reference, corresponding to the uptime at ecore_init. When applying the scenario, this timestamp is checked and gives an idea of a delay to wait before consuming the first event.		2016-03-23 11:42:47 +02:00
..
Makefile.am	Prevent deletion of shots having same prefix as test name	2015-06-09 13:52:53 +01:00
exactness_private.h	Prevent deletion of shots having same prefix as test name	2015-06-09 13:52:53 +01:00
tsuite_evas_hook.c	Support reference timestamp	2016-03-23 11:42:47 +02:00
tsuite_file_data.c	Support reference timestamp	2016-03-23 11:42:47 +02:00
tsuite_file_data.h	Support reference timestamp	2016-03-23 11:42:47 +02:00