BUG: L10 UI designers - I still hate the lack of a mouse control go

Yes, I still want the arrow/go returned to the search box. This having to take my hand off the mouse and put it on the keyboard only to immediately return it to the mouse is still a poor interface design that is an annoyance every time I have to do it.

Find more posts tagged with

Desktop App

Comments

NB.Mick

JT (alabama24)

I don't understand. Is this only on windows? (There is an arrow on Mac). Also, if you are TYPING something into the go box, your hand isnt on the mouse... it is on the keyboard. I fully admit that you are smarter than me so what am I missing?

Kiyah

Yes, I still want the arrow/go returned to the search box. This having to take my hand off the mouse and put it on the keyboard only to immediately return it to the mouse is still a poor interface design that is an annoyance every time I have to do it.

Agreed. You actually can't run a saved Morph Query without opening the query and running it from there now (something I'll be reporting in a separate post). Ridiculous.

NB.Mick

I don't understand. Is this only on windows? (There is an arrow on Mac).

Hm. I don't recall Mac-users stepping in when this bad design decision - which they took on purpose, even if I don't see or recall why - was flagged in the beta tests.

To be clear about it, this is the issue

...and I keep finding myself at the mouse and then navigating to the box, clicking in it and then hitting return, whishing I just could click a button instead.

MJ. Smith

if you are TYPING something into the go box,

That is a big IF ... I often am not. IF I were typing something and the last thing I did was build the search argument rather than adjust settings, then it would not be an issue. However, the design of the Context Menu encourages copy & paste for the search argument rather than typing. I am also often running a search to refresh the results.

Eli Evans (Logos)

I'll discuss with Mark. Thanks!

MJ. Smith

I'll discuss with Mark. Thanks!

Would it help or hinder you if formal use cases were offered when we think a poor design decision was made? It sometimes seems like it takes forever to get FL to understand why a design doesn't work - the lack of an export on search results being another example, although not one that affects me personally.

JT (alabama24)

Hm. I don't recall Mac-users stepping in when this bad design decision - which they took on purpose, even if I don't see or recall why - was flagged in the beta tests.

Are you mad at me?

I don't understand how you are getting text into the box without typing it.

Eli Evans (Logos)

I don't understand how you are getting text into the box without typing it.

I'm interested in the exact details of that part of the interaction as well ... I assume something like right-click copy and paste, but that may not be it.

NB.Mick

Hm. I don't recall Mac-users stepping in when this bad design decision - which they took on purpose, even if I don't see or recall why - was flagged in the beta tests.

Are you mad at me?

Not at all.

It just didn't occur to me that Faithlife would have purposely changed the design of such a relevant feature as search only for Windows, so I kinda expected it to look the same for you guys.

MJ. Smith

Ways in which I have NOT just typed something into the search argument:

1. I have a viseral dislike for many of the FL defaults to broader searches than I am interested in although I understand the rationale behind them and do not wish to request a change. Therefore, I always have my parameters set to the narrowest possible searches. When I see the results, I choose to broaden the settings based on my results. I am changing only settings not the search argument so I want to simply click "go" after I modify the parameters.

2. I often use a search to create work lists. As I work through the work list, the search results should change. I simply want to refresh my results i.e. click "go".

3. I frequently use the copy function of the Context Menu to generate the search argument because the corpus of resources I wish to search is not covered by the Context Menu searches.

4. When I am looking through the search results, I often find something a want to add to my search argument, building something like this: [quote]

”Acts of Andrew” OR “Acts Andr” OR ActAndr OR “Acta Andreae” OR “Passio of Andrew” OR “Miracles of Andrew” OR “Liber de Miraculis Beati Andreae” OR “Acts and Martyrdom of the Holy Apostle Andrew” OR “Andreas-Akten” OR “Martyrium prius” OR “Martyrium alterum B” OR “Martyrium alterum A” OR “Gospel of Andrew” OR “Liber de virtutibus sancti Andreae apostoli” OR “Apocryphal Acts of Andrew” OR “Actes d’André grecs” OR “The Acts of Andrew the Apostle”

My usual way to add an addition term is to type OR "", then go to my current results to do a copy and return to the search argument for the paste ... leaving my hand on the mouse when "go" is the next action.

5. Least common reason, I have restored an argument from the search history and need to click go.

Those are my five most common use cases where I miss the click arrow go function.

Note: for tagging resources with their preferred Bibles, I use the search argument "scripture quotations from" OR "All scripture quotations" OR "unless otherwise indicated" OR "authors own translation" OR "Scripture text used in" OR "Scripture quotations are from" OR "Scripture quotations unless otherwise noted" OR "Scripture quotations are taken" OR "Scripture verses are from" OR "biblical citations are taken from" OR "scripture quotations marked" OR "all Scripture quotations in this publication" OR "Scripture references are taken from" OR "Scripture quoted from" OR "Scripture taken from" OR "all Scripture unless otherwise" OR "all scripture citations" OR "All Scripture is taken from" OR "scripture references marked" OR "Scripture quotations in this publication" OR "scripture quotations labeled" OR "All Bible quotations are taken" OR "Scripture quotations contained herein" OR "Biblical quotations unless otherwise specified" OR "Bible quotations in this publication" OR "scripture marked"

NB.Mick

I don't understand how you are getting text into the box without typing it.

For example just now. I had this "cookbook" search from the page, Jesus AND Christ (for the screenshot I had typed it by hand, now I just clicked on the cookbook phrase), it had executed an All search - silly me, of course I had expected to get a bible search. I clicked on "Bible" and it ran against my trusted NIV - with the small hick-up that I had to activate the field and hit return.

This happens to me. Or switching from a Morph search to Bible. Or that I change something at the beginning if the string and immediately pick up the mouse (learned from years of Logos usage) and then see I have to position and then get back to the keyboard. Sometimes the wireless keyboard sits elsewhere - I just think I'm a mouse-person, others are keyboard persons.

Eli Evans (Logos)

Very helpful context, thanks!