LPEX
3.6.6

com.ibm.lpex.core
Interface LpexViewListener

All Known Implementing Classes:
CursorHairline, LpexViewAdapter, MouseReselect

public interface LpexViewListener

Listener to document view events.

You may implement this interface to create a document view listener. Create a listener object using this class, and then register it with a document view using the view's addLpexViewListener() method. When an event occurs, the relevant method in the listener object is invoked.

It is recommended that you use the LpexViewAdapter class to create your document view listener.

See Also:
LpexView.addLpexViewListener(com.ibm.lpex.core.LpexViewListener), LpexView.removeLpexViewListener(com.ibm.lpex.core.LpexViewListener), LpexViewAdapter

Method Summary
 void disposed(LpexView lpexView)
          This method is invoked when the document view is disposed.
 void readonly(LpexView lpexView)
          This method is invoked after an attempt has been made to edit a read-only document.
 void renamed(LpexView lpexView)
          This method is invoked after the document name, source name, or view id has changed.
 boolean renaming(LpexView lpexView)
          This method is invoked just before the document or source name is changed.
 void saved(LpexView lpexView)
          This method is invoked after the document has been saved by the LPEX widget.
 boolean saving(LpexView lpexView)
          This method is invoked just before the document is saved by the LPEX widget.
 void showing(LpexView lpexView)
          This method is invoked just before the screen is displayed.
 void shown(LpexView lpexView)
          This method is invoked after the screen display is complete.
 void updateProfile(LpexView lpexView)
          This method is invoked after the updateProfile editor command has completed processing.
 

Method Detail

showing

void showing(LpexView lpexView)
This method is invoked just before the screen is displayed. The screen is rebuilt and displayed after every user action. It is also rebuilt and displayed when the screenShow editor command is issued.

See Also:
shown(com.ibm.lpex.core.LpexView)

shown

void shown(LpexView lpexView)
This method is invoked after the screen display is complete.

See Also:
showing(com.ibm.lpex.core.LpexView)

saving

boolean saving(LpexView lpexView)
This method is invoked just before the document is saved by the LPEX widget. If you return true, then the remaining listeners will not be invoked and the save will be aborted.

This notification is not issued for "save as" operations. Also, an LPEX-based application may do its own save, bypassing the widget's save to the local file system.

See Also:
saved(com.ibm.lpex.core.LpexView)

saved

void saved(LpexView lpexView)
This method is invoked after the document has been saved by the LPEX widget.

This notification is not issued for "save as" operations. Also, an LPEX-based application may do its own save, bypassing the widget's save to the local file system.

See Also:
saving(com.ibm.lpex.core.LpexView)

renaming

boolean renaming(LpexView lpexView)
This method is invoked just before the document or source name is changed. If you return true, then the remaining listeners will not be invoked and the rename will be aborted.

See Also:
renamed(com.ibm.lpex.core.LpexView)

renamed

void renamed(LpexView lpexView)
This method is invoked after the document name, source name, or view id has changed.

See Also:
renaming(com.ibm.lpex.core.LpexView)

readonly

void readonly(LpexView lpexView)
This method is invoked after an attempt has been made to edit a read-only document.


updateProfile

void updateProfile(LpexView lpexView)
This method is invoked after the updateProfile editor command has completed processing.


disposed

void disposed(LpexView lpexView)
This method is invoked when the document view is disposed.


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.