LPEX
3.6.7

com.ibm.lpex.samples
Class TestUserProfile.CloseJoin

java.lang.Object
  extended by com.ibm.lpex.samples.TestUserProfile.CloseJoin
All Implemented Interfaces:
LpexAction
Enclosing class:
TestUserProfile

public static class TestUserProfile.CloseJoin
extends Object
implements LpexAction

Sample action closeJoin - join with just one space between the texts. This action is similar to the join default editor action, but it will keep one and only one space between the joined lines.

Defined as a separate, named class inside TestUserProfile (where you can also see its source code) so that it can be easily registered by itself, when TestUserProfile is not used as the user profile. For example:

   set actionClass.closeJoin com.ibm.lpex.samples.TestUserProfile$CloseJoin
   set keyAction.a-j closeJoin


Constructor Summary
TestUserProfile.CloseJoin()
           
 
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

TestUserProfile.CloseJoin

public TestUserProfile.CloseJoin()
Method Detail

doAction

public void doAction(LpexView lpexView)
Runs the action. Joins the current and next text lines, keeps one space (no more, no less) between the concatenated texts.

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 can be run in any visible, writable document view.

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

LPEX
3.6.7

Copyright © 2012 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.