Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.rse.ui.view.errorlist
Class QSYSErrorListRemovedMessagesFilter

java.lang.Object
  extended by ViewerFilter
      extended by com.ibm.etools.iseries.rse.ui.view.errorlist.QSYSErrorListRemovedMessagesFilter

public class QSYSErrorListRemovedMessagesFilter
extends ViewerFilter

This class is used to keep track of any errors with have been removed from the error list.

Since:
6.0 57723A

Field Summary
static String Copyright
           
 
Method Summary
 void addRemovedMessage(IMarker marker)
          add the specified marker/messages to the list of removed messages.
 void addRemovedMessages(IStructuredSelection selection)
          Add a list of markers/messages to the list of removed messages.
 void clearMessageList()
           
 boolean select(Viewer viewer, Object parentElement, Object element)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

Copyright

public static final String Copyright
See Also:
Constant Field Values
Method Detail

select

public boolean select(Viewer viewer,
                      Object parentElement,
                      Object element)

addRemovedMessage

public void addRemovedMessage(IMarker marker)
add the specified marker/messages to the list of removed messages.

Parameters:
marker - the marker to add to the list of removed elements.

addRemovedMessages

public void addRemovedMessages(IStructuredSelection selection)
Add a list of markers/messages to the list of removed messages.

Parameters:
selection -

clearMessageList

public void clearMessageList()

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.