View Single Post
Old 07-22-2024, 09:12 AM   #11
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,450
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by Phssthpok View Post
You miss my point. I want to test the thing I want to test ("here is some input, show me the corresponding output"), not a modified version of it. Otherwise when I modify it back again, I have to test it again, but I can't test it except by doing what I was doing before -- loading a book onto my device and checking that the result is correct -- because the available tools do not allow me to test it as-is, without modification.
You're right, I don't understand. The template tester shows the output of the template for every book selected when the tester is opened. You control which books are selected so you can see a range of inputs. The tester shows exactly what the metadata plugboard will generate and send to the device. You can look at the metadata for the selected books while the tester is open.

If what you want to do is modify book metadata (template input) even temporarily inside the tester then that won't happen.
chaley is offline   Reply With Quote