-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
Search Toolbar visibility #158
Comments
I would implement this feature like this:
What do you think? |
My intention behind this issue was to save time by not having to click anywhere or activate something to be able to search. When implemented the way you described I'll always have to delete the text entered in the search bar to get rid of the additional elements - thus I'm losing time. |
I understand your intention but you can activate/focus the search bar using F3. |
this sounds ok to me - especially the ESC key. |
I agree with eusebiu about F3: there really is no need to change anything. However, if we're dreaming about the ultimate user experience, ideally a small search box should always be visible, right aligned in the toolbar. And it should look and behave more or less like the search box in FireFox or IE8. |
I agree with Kris. The search input should be in the right part of the toolbar and be always visible. Once you search the current panel is shown. |
I'm closing this issue; we currently have no intentions of changing this. |
Yet another one on search experience ;-)
I think it would be more comfortable if the search bar would be visible on ILSpy start up.
Searching for types or members is imho the #1 use case when using ILSpy so why enforce this additional click every time you start ILSpy?
The text was updated successfully, but these errors were encountered: