|
Eclipse Platform Release 3.1 |
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
An editor matching strategy allows editor extensions to provide their own
algorithm for matching the input of an open editor of that type to a
given editor input. This is used to find a matching editor during
IWorkbenchPage.openEditor(IEditorInput, String, boolean)
and
IWorkbenchPage.findEditor(IEditorInput)
.
Method Summary | |
---|---|
boolean |
matches(IEditorReference editorRef,
IEditorInput input)
Returns whether the editor represented by the given editor reference matches the given editor input. |
Method Detail |
public boolean matches(IEditorReference editorRef, IEditorInput input)
Implementations should inspect the given editor input first,
and try to reject it early before calling IEditorReference.getEditorInput()
,
since that method may be expensive.
editorRef
- the editor reference to match againstinput
- the editor input to match
true
if the editor matches the given editor input,
false
if it does not match
|
Eclipse Platform Release 3.1 |
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Guidelines for using Eclipse APIs.
Copyright (c) IBM Corp. and others 2000, 2005. All rights reserved.