platform search

This document lists the breaking API changes that occurred between R3.2 and R3.3 and how to migrate from the R3.2 API to the R3.3 API.

search - Breaking API changes from R3.2 to R3.3
None

search - Non-breaking API changes from R3.2 to R3.3
New constant added to org.eclipse.search.ui.IContextMenuConstants
  • GROUP_EDIT
  • GROUP_FILTERING
Added support for match filters:
  • Added class MatchFilter (org.eclipse.search.ui.text): MatchFilters are managed by the AbstractTextSearchResult and used to update the filter state of a match (see Match.isFiltered()). Filtered matches are still part of the search result but are not shown in the AbstractSearchViewPart and rendered as 'filtered search result' in editors
  • New API in AbstractTextSearchResult (org.eclipse.search.ui.text):
    • getAllMatchFilters(): All match filters applicable on this search result. If non-nuill is returned, the AbstractSearchViewPart will add corresponding filter actions to the view menu
    • getActiveMatchFilters(): All match filters currently applied to this search result
    • setActiveMatchFilters(): Update filters
  • Added class FilterUpdateEvent (org.eclipse.search.ui.text): FilterUpdateEvents are sent out when filters are updated by AbstractSearchResult.setActiveMatchFilters(..). The AbstractSearchViewPart listens to these changes and takes care of adding or removing filtered elements
  • Added API to AbstractTextSearchViewPage (org.eclipse.search.ui.text): getElementLimit, setElementLimit

API changes from 3.1 to 3.2 can be found here.