LPEX
4.4.0

com.ibm.lpex.samples
Class FindNextDefaultAction

java.lang.Object
  extended by com.ibm.lpex.samples.FindNextDefaultAction
All Implemented Interfaces:
LpexAction

public class FindNextDefaultAction
extends Object
implements LpexAction

Sample action findNextDefault - find next default text occurrence. This action is similar to the findNext built-in editor action, but will find the next occurrence of the global-scoped find text (default.findText.findText), rather than the current view-scoped find text. The global find text is usually set to the text lately searched from the live-find dialog of any view.

Here is the FindNextDefaultAction source code.

To run this sample:

See Also:
All the samples

Constructor Summary
FindNextDefaultAction()
           
 
Method Summary
 boolean available(LpexView lpexView)
          Returns the availability of this action.
 void doAction(LpexView lpexView)
          Runs the action.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

FindNextDefaultAction

public FindNextDefaultAction()
Method Detail

doAction

public void doAction(LpexView lpexView)
Runs the action. Finds the next occurrence of the default find text.

Specified by:
doAction in interface LpexAction
Parameters:
lpexView - the document view in which the action is issued

available

public boolean available(LpexView lpexView)
Returns the availability of this action. This action is enabled whenever there is text to find.

Specified by:
available in interface LpexAction
Parameters:
lpexView - the document view for which the action availability is queried

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.