## org.das2.qds.filters.AbstractFilterEditorPanel

Implements the typical filter, where we don't care about the input data and the filter itself implements the GUI. Note when the filter property would change, the implementation must fire off a property change.

## AbstractFilterEditorPanel( )

## getFilter

getFilter( ) → String

return the filter specified by the GUI. The filter string will start with the pipe character. When this would change, implementations should fire off a property change event like so:

>     firePropertyChange( PROP_FILTER, null, ff );

where ff is the new value.

### Returns:

the filter string
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## getPanel

getPanel( ) → javax.swing.JPanel

### Returns:

javax.swing.JPanel
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## setExpertMode

setExpertMode( boolean expert ) → void

### Parameters

expert - a boolean

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## setFilter

setFilter( String filter ) → void

configure the GUI based on this filter. The filter string will start with the pipe character.

### Parameters

filter - the filter string

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## setInput

setInput( QDataSet ds ) → void

### Parameters

ds - a QDataSet

### Returns:

void (returns nothing)
[search for examples] [view on GitHub] [view on old javadoc] [view source]

## validateFilter

validateFilter( String filter, QDataSet in ) → boolean

### Parameters

filter - a String
in - a QDataSet

### Returns:

boolean
[search for examples] [view on GitHub] [view on old javadoc] [view source]