Jump to content


Photo

Keeping focus on the search field


  • Please log in to reply
2 replies to this topic

#1 jlm

jlm

    Member

  • Active Members
  • Pip
  • 38 posts
  • Gender:Male
  • Accordance Version:12.x
  • Platforms:Mac OS X, iOS

Posted 01 March 2019 - 12:23 PM

I would like to suggest a minor refinement to the search interface, which consists of a text field and some buttons that pop up menus for selecting the database, setting options, etc. My suggestion is simply this: after the user has used one of the menus, restore the focus to the search field so that it is possible to hit Enter to search or type more text for the search. It's a small thing, but it would speed up searches.

As it is, I find that I always have to tap on the text field again after using a menu. Here are some examples:
- I amplify a lexeme, and Want to see it in a different lexicon: I tap seach, tap the button to select the lexicon, and have to tap again on the text field to be able to hit enter to search.
- I am reading a Bible and want to search it. I tap search, type my seach, tap Options to select a range, and have to tap the search field again so that I can hit Enter to search.

#2 Brian W. Davidson

Brian W. Davidson

    Silver

  • Active Members
  • PipPipPip
  • 161 posts
  • Gender:Male
  • Accordance Version:12.x
  • Platforms:Mac OS X, iOS

Posted 01 March 2019 - 12:46 PM

I noted this at some point, but can’t find where. The thing is that the problem you’re noting happens on the iPad, but it doesn’t behave that way on the iPhone. On the iPhone app the cursor automatically returns to the search field.

I was bugged by the iPad app problem this morning, but was thinking that since the new, big update was just around the corner, maybe that would fix it.

Thanks for bringing the issue back up.

#3 Brian W. Davidson

Brian W. Davidson

    Silver

  • Active Members
  • PipPipPip
  • 161 posts
  • Gender:Male
  • Accordance Version:12.x
  • Platforms:Mac OS X, iOS

Posted 06 March 2019 - 02:45 PM

This issue has been fixed in the latest beta of 2.7.4 that was released today.
  • jarcher likes this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users