iSeries Remote Systems
v6.0.0

com.ibm.etools.iseries.core.ui.view.errorlist
Class ISeriesErrorListRemovedMessagesFilter

java.lang.Object
  extended byorg.eclipse.jface.viewers.ViewerFilter
      extended bycom.ibm.etools.iseries.core.ui.view.errorlist.ISeriesErrorListRemovedMessagesFilter

public class ISeriesErrorListRemovedMessagesFilter
extends ViewerFilter

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

Since:
6.0 57723A

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 org.eclipse.jface.viewers.ViewerFilter
filter, isFilterProperty
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

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()

iSeries Remote Systems
v6.0.0

Copyright © 2005 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.