The current EditorSearchOptions.Scope is an enumerated property. It only has two enumeration items, Document and Selection.
What should I do if I want to add a Project scope search.
Comments (2)
Hello,
The editor itself only knows how to search through the document and selection scopes. At the current time, you'd have to use your own search UI instead if you wish to support custom search scopes.
We are open to suggestions for the future on adding extensibility to support other search scopes. Please post any ideas you have on API additions that would allow you to hook in, list custom search scopes in our search UI, and respond to searches in those custom search scopes.
Actipro Software Support
My idea is that the search scope should support expansion. Users can implement custom search scope providers by themselves.
After all, it is impossible to search only the current document in most languages. So it’s important to provide users with expansion capabilities.
The latest build of this product (v24.1.1) was released 2 months ago,
which was after the last post in this thread.
Add Comment
Please log in to a validated account to post comments.