Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion: show the number of matches when running a search #1476

Closed
rickmed opened this issue Dec 19, 2015 · 16 comments
Closed

Suggestion: show the number of matches when running a search #1476

rickmed opened this issue Dec 19, 2015 · 16 comments
Assignees
Labels
feature-request Request for new features or functionality verified Verification succeeded
Milestone

Comments

@rickmed
Copy link

rickmed commented Dec 19, 2015

No description provided.

@rickmed rickmed changed the title Suggestion: show find ocurrences on find command Suggestion: show find ocurrences with find command Dec 19, 2015
@bpasero
Copy link
Member

bpasero commented Dec 19, 2015

@ricmed205 can you clarify what you want?

@bpasero bpasero added the info-needed Issue requires more information from poster label Dec 19, 2015
@rickmed
Copy link
Author

rickmed commented Dec 19, 2015

Yes! I wast just editing. Sorry.
When using the find in file feature (ctrl+f), show the number of matches when running a search.

@bpasero bpasero changed the title Suggestion: show find ocurrences with find command Suggestion: show the number of matches when running a search Dec 19, 2015
@bpasero bpasero added feature-request Request for new features or functionality and removed info-needed Issue requires more information from poster labels Dec 19, 2015
@bpasero bpasero added this to the Backlog milestone Dec 19, 2015
@bpasero
Copy link
Member

bpasero commented Dec 19, 2015

Ok thanks.

@bpasero
Copy link
Member

bpasero commented Dec 23, 2015

@alexandrudima fyi

@rhbecker
Copy link

rhbecker commented Jan 7, 2016

+1

... and along those same lines, it would be useful to see the "index" of the currently highlighted match; e.g. if there are 20 matches and the 14th is highlighted, I'd see 14/20, and find next / find previous would increment / decrement the index, respectively.

@alexdima alexdima self-assigned this Jan 14, 2016
@alexdima
Copy link
Member

@rhbecker I've just pushed a few days ago a match counter, but it doesn't show at this time X of Y, it just shows Y:

image

@stevencl
Copy link
Member

I would consider putting the label x of y next to the next and previous arrows rather than next to the search options. For example (without and with a border around the x of y label below)

xofy

Just to check though, what is the UX problem that we are trying to solve with this? Is it that without this, the user is unaware when they have reviewed all of the search results? Or is this solving another UX problem? That could help determine how important it is to show an x of y label.

How should search results be indexed? I think I would expect, if I wanted to be aware when I have reviewed all of the search results, that the result labeled 1 of y should be the first result found after the current insertion point, rather than the first item in the file.

@alexdima
Copy link
Member

@stevencl Wow that looks so much better and makes a lot of sense to put them next to the prev/next buttons 👍

How should the replace buttons be aligned then?:
image

I personally would expect them to be always indexed from the top and then you'd start at "5 of 14" if that would be the next match. That is what Chrome's find does for example.

I am not sure what the underlying UX problem is, we have always been asked to show some numbers in there. Maybe @chrisdias and @ricmed205 can add more details.

@stevencl
Copy link
Member

Starting at 5 of 14 would work too I think, that sounds good.
I would continue to align the replace buttons next to the right edge of the replace text box. Fortuitously, this also means that the replace button sits underneath the index and the replace all button sits underneath the count :-).
xofyreplace

@rickmed
Copy link
Author

rickmed commented Jan 14, 2016

"5 of 50" just like Chrome is perfect -where the index starts at the top of the doc.

@stevencl 👍 UX
" Is it that without this, the user is unaware when they have reviewed all of the search results?" <- This

@rhbecker
Copy link

@alexandrudima

Your responsiveness to our suggestions is very much appreciated!

@stevencl

what is the UX problem that we are trying to solve with this?

In addition to what's already been stated ...

I find y useful in determining whether to add more detail to my query.

I type "dog" on my way to "doggy". I'm lazy, so as soon as typing "dog" gets me to a small y, I'll start tabbing through results. Maybe I was inconsistent in my usage of the "gy" suffix, and it's handy to see that some of my matches are like "dogYears". But maybe "dog" didn't get my y small enough, because someone else used "doge" like 40 times, so I'll keep typing to distinguish, in order to get y smaller - to a quantity that's easier to deal with.

I find x useful as a wayfinding mechanism.

I'm the sort of person who gets confused if I'm not starting at either the beginning or end of a document. If I start in the middle, I'll forget where in the middle, and won't know when I've arrived back at where I started. If I run a search and my x is closer to 1 than y, I'll scroll backward to get to 1 before I start dealing with my matches, while if my x is closer to y, I'll scroll forward to get to y (or will go one more "forward" to circle back to 1) before I start dealing with my matches.

The matches visualization in the scroll bar is nice, but it's also a bit ambiguous. I can't always tell at a glance whether I'm really on the first or last match. Certainly, it doesn't help me know I'm on the 34th match.

If I'm reviewing / discussing a document with someone else, it's handy to say "go to the 8th match".

@alexdima
Copy link
Member

Had some time today to work on this. Given the UX sketch, here's what I could come up with:

A. variable width widget

find-matches-variable

B. fixed width widget, variable width label

find-matches-variable-label

C. fixed width widget, fixed width label

find-matches-stable

My personal favorite is C, since in A and B things float around, which draws attention for no good reason and it feels wierd.

@stevencl Thoughts?

@alexdima alexdima modified the milestones: Jan 2016, Backlog Jan 22, 2016
@stevencl
Copy link
Member

C looks good I think.

Nice work!

@chrisdias
Copy link
Member

👍

@rickmed
Copy link
Author

rickmed commented Jan 22, 2016

@alexandrudima awesome.

Have you tried tried placing the "X of X" inside the label (on the right part), replacing it with caps and regex options? the whole thing would be fixed width

Similar to chrome

@stereokai
Copy link

+1 for C. At least until someone comes up with something aesthetically superior - because the quirky jumpiness of A and B is distractive and impairs the user experience. Great work @alexandrudima 👍

@alexdima alexdima added the verified Verification succeeded label Feb 26, 2016
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Request for new features or functionality verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

7 participants