org.das2.qds.filters.FilterEditorPanel

Interface for adding small GUIs to control each of the filters. For example "|divide(5)" is controlled with a GUI that accepts the float parameter that might check that the operand is not zero. These should each implement get and setFilter, and fire off a property change event when the value is changed, so the GUI can be interactively.

PROP_FILTER

getFilter

getFilter( ) → String

return the filter specified by the GUI. The filter string will start with the pipe character. This may be called from off of the event thread!

Returns:

the filter string

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

getPanel

getPanel( ) → javax.swing.JPanel

the panel for this editor.

Returns:

the panel for this editor.

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

setExpertMode

setExpertMode( boolean expert ) → void

If false, then remove options which might break products.

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

configure the GUI based on this input

Parameters

ds - the data that will be input to the filter

Returns:

void (returns nothing)

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

validateFilter

validateFilter( String filter, QDataSet in ) → boolean

return true if the filter is valid

Parameters

filter - "slice1(-1)"
in - the input, or null.

Returns:

false if the input is clearly not valid.

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