Nothing is quietly dropped
- Clipping a page from the bookmarklet tells you it worked. It set an address and the browser showed no sign at all that anything had happened, so there was nothing to do but wait and wonder — and clicking again, which clipped the page a second time. It now says Sent to MojoPad on the page itself the moment you click, and a second click while you are waiting says the first one is still on its way instead of sending another.
- A caveat about an answer travels with the answer. When a run ends without everything you asked for — a server that could not be reached, a tool that refused — MojoPad says so under the answer. That warning was drawn on screen and kept nowhere, so it lasted exactly one viewing: inserting the answer into a page, saving it as a page, or saving a whole conversation all carried the words and left the caveat behind, and reopening the conversation from
lost it there too. It now goes wherever the answer goes, and in a page it stays as a quoted note above your own writing. An answer that arrives in a page without it reads as complete, and the only person who would know otherwise is the one who watched it fail. - A property holding several answers arrives as several answers. Exported to a web page, a PDF or Word, a property with more than one answer was joined into a single line with commas — which reads perfectly for a row of tags and falls apart the moment the answers are sentences, since every full stop then has a comma after it and a list of findings becomes one long unreadable sentence. Answers short enough to sit on one line still do; anything longer is written out as a list, in each of those formats and as indented lines in plain text.
- A list short enough to read no longer offers a box to search it. A chooser with two options put a filter above them. There is no answer to what you would type.