(Despite my giving a list of 11 things to fix, don't think your work isn't appreciated! Thanks for the improvements already made. I'm looking forward to v. 1.3.1 --- and even more to 1.4. )
1. What is the official purpose of the book icon in top left? I can tell that at least one thing it does is hide the search bar--but it doesn't toggle, so you can't get the search bar back after it's hidden. Why would you use a book icon to indicate hiding a search bar?! At the least, this isn't intuitive. I must be missing something here...
As Joel said, this button is used to clear the current search results and return the user to what we are calling "Reader" or "Reading" mode. It's really a shortcut to run the default search which uses a search text of the asterisk wildcard character and sets the search mode to Verses. As a bonus, we also scroll the text to the same verse location that was being displayed at the top of the text view.
I agree this can be confusing and less than ideal. So we are exploring other options, particularly in conjunction with adding some type of search history feature.
2. When entering a GNT-T search with an English version in the top pane and GNT-T in bottom pane, running the search changes the tip pane to GNT-T. That leaves BOTH panes Greek! Grrr! Should either run the search in the bottom pane (as Mac app would) or at the least reverse the two panes and put Eng in bottom. (At least it's now easier to change the versions/texts displayed.)
This is a difference in how Accordance for Mac and iOS work with regards to search texts and display texts. In Accordance for iOS the search text and display text are ALWAYS
the same. So choosing a different module in the search interface not only runs the search against the chosen module, but switches the display text to this module also if the search is successful.
3. Tag button sometimes left grayed out and non-functioning; have to tap Commands button 2x to get Tag button to be usable.
This looks like a bug.
4. Ought to be a Search button in the Search bar instead of only the default keyboard search button. (That's where your finger often is when you're entering search commands...)
We're using the system supplied search bar and the system supplied keyboard. This combination is what supplies the "Cancel" button you see next to the search bar and the "Search" button on the keyboard. And because we are trying the keep the search interface as "common" between the iPhone and iPad platforms, I don't really see the benefit of creating a more custom interface, particularly when we really don't have the screen real estate on the iPhone for the button.
5. When an invalid search criteria is entered the error msg. is "No results found." That's not helpful; it should say there is an invalid criteria entered as in Mac version. Even if you can't give as many specifics as the desktop app, at least tell the user it's an error, not a valid search with no results.
I agree it's not helpful. And it's really a placeholder until we bring over our localization code which drives the text of the various error messages. It's definitely on the list to change.
6. Greek font doesn't appear in search bar when typing.
Ahh. Another difference between Accordance for iOS and Mac. Because we are using the system supplied search bar, text entry is now in terms of Unicode and not a custom Accordance interpretation of Mac Roman characters. And we don't have control to dynamically change the characters as they are being entered. So if you want to type Greek text, then turn on the Greek keyboard in the Settings app and switch to it for entering Greek characters. Same for Hebrew.
Note that if you do enter MacRoman characters for Greek and Hebrew, we do try to "interpret" them as appropriate when performing the search and display the translation of the search term. But it is a fairly fragile system at the moment particularly when mixing search commands and tags (which are English based) and Unicode text entry. We'll improve it as we can.
7. No word lists for lexical or inflected forms. That would be very helpful if for some reason you can't display mixed languages in the search field (#6).
8. Font size buttons are sorely missed, esp. on iPhone, but even iPad would make work flow much simpler.
Both on the feature list.
9. Need navigation controls other than just finger scroll. Next hit/verse/chapter/book, etc. (At one point I saw some grayed arrow heads in bottom margin that I hoped were these sort of controls, but they didn't do anything.)
The left/right arrows in the bottom toolbar do function as next/previous location navigation just like they do in Accordance for Mac. Use the GoTo view to change your location, or tap on a hyperlink in a tool search view and note that these arrows will enable or disable as appropriate to move you back and forth through the text.
The up/down arrows are equivalent to the previous/next bookmark arrows in Accordance for Mac. So they are only enabled when your search results are being viewed in terms of the entire module. (All Context in text modules). I agree that we could possible have them do "double" duty when in the reading mode of a search view. The question is what is the extra functionality by default? Wouldn't it be confusing to users to have these buttons change their operation based on the mode? And while there may be enough room on the iPad to add all the various navigation arrows we have in Accordance for Mac, there is no way we can do that for iPhone.
We also talked about adding gestures as shortcuts for some of these navigation needs, but haven't agreed or finalized a specification yet.
10. Entry of search criteria is much faster if typed manually for those who know the search syntax. For those who don't, there is no way to enter related criteria, e.g., you can use Tags to enter [verb], but then you can't specify, say, [verb aorist middle indicative]. There ought to be either a dialog or popup to specify this.
11. When typing in search criteria manually, the keyboard requires going 3 levels deep to access the square bracket keys--which are used constantly in grammatical searches! Grrr! There must be a better way to do this, ideally with a specialized keyboard for at least iPad version that would put the most commonly used keys on main keyboard (like browser keyboards do with slash and suffixes, etc.), ideally on iPad with a numerical keypad too! (even if accessing that were only possible in landscape mode). If for some reason that isn't possible technically (I didn't say "easily! ) then at least give us pop-ups with the needed symbols.
We really, really don't want to write a custom keyboard. The real solution would be to make the Tags entry easier. We've had it on our feature list to "translate" the set of complicated dialogs for entering Tags in Accordance for Mac to a set of hierarchical table lists so users would not have to perform any (or a very minimal) amount of typing. But, as I said, it's pretty complicated. Are you volunteering for the work?
Thanks for all the feedback,