From 60adbd88c388054042094eec0ccf3e0e72957377 Mon Sep 17 00:00:00 2001 From: Thomas Schmitt Date: Wed, 23 Sep 2015 11:07:24 +0000 Subject: [PATCH] Mutally mentioned the other demo program in their introdution comments --- libburn/trunk/test/libburner.c | 2 ++ libburn/trunk/test/telltoc.c | 3 ++- 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/libburn/trunk/test/libburner.c b/libburn/trunk/test/libburner.c index 7c1c7178..22904453 100644 --- a/libburn/trunk/test/libburner.c +++ b/libburn/trunk/test/libburner.c @@ -16,6 +16,8 @@ to serve the libburnia team as reference application. libburner.c does indeed define the standard way how above three gestures can be implemented and stay upward compatible for a good while. + There is another demo program, test/telltoc.c, which inspects drive, media + state, and media contents. Before you can do anything, you have to initialize libburn by burn_initialize() diff --git a/libburn/trunk/test/telltoc.c b/libburn/trunk/test/telltoc.c index b0e57445..1f9b0807 100644 --- a/libburn/trunk/test/telltoc.c +++ b/libburn/trunk/test/telltoc.c @@ -14,6 +14,7 @@ to serve the libburn team as reference application. telltoc.c does indeed define the standard way how above gestures can be implemented and stay upward compatible for a good while. + The burn aspects of libburn are demonstrated by program test/libburner.c . Before you can do anything, you have to initialize libburn by burn_initialize() @@ -964,6 +965,6 @@ finish_libburn:; } /* License and copyright aspects: - See libburner.c + See test/libburner.c */