LPEX
3.6.7

com.ibm.lpex.samples
Class SetDateAction.SetDate

java.lang.Object
  extended by com.ibm.lpex.samples.SetDateAction.SetDate
All Implemented Interfaces:
LpexCommand
Enclosing class:
SetDateAction

public static class SetDateAction.SetDate
extends Object
implements LpexCommand

Sample command setDate - set the sequence-numbers date in the selected range. Use this command to modify the textual part of the sequence numbers in all the currently-selected visible lines. If you do not specify the new text via the command parameter, you will be prompted for it. Note that LPEX doesn't record changes to the sequence numbers in its undo stack.

This is an alternative to the setDate sample action, for cases in which the user prefers the command approach, or is running out of available keys to assign to actions.

Defined as a separate, named class inside SetDateAction (where you can also see its source code), it can be registered in the editor with, for example:

   set commandClass.setDate com.ibm.lpex.samples.SetDateAction$SetDate

and run from the command line:
   setDate [ newDate ]


Constructor Summary
SetDateAction.SetDate()
           
 
Method Summary
 boolean doCommand(LpexView lpexView, String parameters)
          Runs this command.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

SetDateAction.SetDate

public SetDateAction.SetDate()
Method Detail

doCommand

public boolean doCommand(LpexView lpexView,
                         String parameters)
Runs this command. Uses the specified date, or otherwise prompts the user for one, and updates the sequence numbers of all the visible selected lines.

Specified by:
doCommand in interface LpexCommand
Parameters:
lpexView - the document view in which the command was issued
parameters - optional new date to set

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.