Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.edit.compile
Interface IISeriesCompileErrorInfoViewHandler

All Known Implementing Classes:
ISeriesEditorCLParser, ISeriesEditorCobol400SqlCicsParser, ISeriesEditorCobolILESqlCicsParser, ISeriesEditorCPPParser, ISeriesEditorDDSParser, ISeriesEditorParser, ISeriesEditorRPGILEParser, ISeriesEditorRPGILESQLParser, ISeriesEditorRPGOPMParser

public interface IISeriesCompileErrorInfoViewHandler

Handler for compile messages to enable the compile messages to be properly added to a secondary editor view need to do this since LPEX does not notify changed marks in secondary views properly should be able to remove this with LPEX 3.1

Since:
6.0.1

Method Summary
 void copyCompileErrorInfo(LpexView secondaryView)
          Used to copy the compile message markers from the primary view to the newly opened secondary view.
 void setCompileErrorInfo(ISeriesCompileEditManager editManager, String markNames, QSYSErrorMarkerListener errorMarkerListener)
          Used to set the compile information to be used when splitting a view so that errors appear in the splits.
 

Method Detail

setCompileErrorInfo

void setCompileErrorInfo(ISeriesCompileEditManager editManager,
                         String markNames,
                         QSYSErrorMarkerListener errorMarkerListener)
Used to set the compile information to be used when splitting a view so that errors appear in the splits.

Parameters:
editManager -
markNames - the list of names of marks in the primary view
errorMarkerListener -
Since:
6.0.1

copyCompileErrorInfo

void copyCompileErrorInfo(LpexView secondaryView)
Used to copy the compile message markers from the primary view to the newly opened secondary view.

Parameters:
secondaryView -
Since:
6.0.1

Rational Developer for Power Systems Software
V7.6

Copyright 2011 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.