LPEX
4.4.0

com.ibm.lpex.alef.contentassist
Interface IContextInformationValidator

All Known Implementing Classes:
ContextInformationValidator

public interface IContextInformationValidator

A context information validator is used to determine whether a displayed context information is still valid at the current cursor position, or should be dismissed.

The interface can be implemented by clients.

This is the LPEX version of org.eclipse.jface.text.contentassist.IContextInformationValidator. It has different methods.

See Also:
IContextInformationPresenter

Method Summary
 void install(IContextInformation info, ITextViewer viewer, LpexDocumentLocation documentLocation)
          Install this validator for the given context information.
 boolean isContextInformationValid(LpexDocumentLocation documentLocation)
          Return whether the information that this validator is installed on, is still valid at the current document location.
 

Method Detail

install

void install(IContextInformation info,
             ITextViewer viewer,
             LpexDocumentLocation documentLocation)
Install this validator for the given context information.

Parameters:
info - the context information which this validator should check
viewer - the LpexTextViewer on which the information is presented
documentLocation - the document location for which the information has been computed

isContextInformationValid

boolean isContextInformationValid(LpexDocumentLocation documentLocation)
Return whether the information that this validator is installed on, is still valid at the current document location.

Parameters:
documentLocation - the current document location
Returns:
true if the information is also valid at the given document location

LPEX
4.4.0

Copyright � 2016 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.