LPEX
3.6.6

com.ibm.lpex.samples
Class BlockNewMarkToMouseAction

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

public class BlockNewMarkToMouseAction
extends Object
implements LpexAction

Sample action blockNewMarkToMouse - start new selections on new mouse drags.

LPEX non-stream selections are by default extended on mouse drags. They must be explicitly cleared (with, for example, Alt+U) before marking a new block. This action is similar to the blockMarkToMouse default editor action, but it makes a new mouse button 1 drag start a new selection.

Here is the BlockNewMarkToMouseAction source code.

To redefine the default blockMarkToMouse action:

See Also:
MouseReselect, All the samples

Constructor Summary
BlockNewMarkToMouseAction()
           
 
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

BlockNewMarkToMouseAction

public BlockNewMarkToMouseAction()
Method Detail

doAction

public void doAction(LpexView lpexView)
Runs the action. It ensures that our mouse-reselect tracking of mouse events is installed in this view, and lets the editor do its regular blockMarkToMouse action.

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 whenever editor's default blockMarkToMouse can.

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

LPEX
3.6.6

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.