Open RichardLuo0 opened 4 months ago
We don't have floating widgets for many functionalities, so I don't think that we'd end up making the search panel floating. But you could try workbench.action.quickTextSearch
to get a 'floating' picker to find items.
The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Happy Coding!
We don't have floating widgets for many functionalities, so I don't think that we'd end up making the search panel floating. But you could try
workbench.action.quickTextSearch
to get a 'floating' picker to find items.
I think you may be misunderstanding. I am not trying to make the search panel floating. I mean in this widget: add an option that lets me open the search result in the search panel: The reason is that the search panel lists all available results and is clearer when you have a single huge file.
Certainly, you can just use the search panel. But then you have to write the glob expression in include files
(assume you need to search only in this file). So for convenience, add an option to the search widget, that allows us to open the results directly in the search panel.
In fact similar function is implemented in Android Studio as well. It opens this:
So you want to see the results of the find
widget in a panel? If you use Quick Search
, the results from the current file should be shown first, if that helps.
Quick Search
is across files, which is different from the search widget which searches the current file only.
It will list the current file's matches first.
Otherwise, if that's not sufficient, I'll pass this over to the feature owner for the find
widget.
Similar to
open results in find window
in Android Studio. Just for convenience.