Bug 325087 - Allow use of user defined scalars in filter plugins
Summary: Allow use of user defined scalars in filter plugins
Status: RESOLVED FIXED
Alias: None
Product: kst
Classification: Applications
Component: ui (show other bugs)
Version: 2.0.7
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kst
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-19 11:20 UTC by david.mcminn
Modified: 2013-09-24 20:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description david.mcminn 2013-09-19 11:20:48 UTC
I can create a scalar value, for example named manually as "Order" with a generated value of 33. The data manager shows the scalar is "Order (X1)" with 1 sample and the value 33.
If I then go to create a filter plugin (Low Pass Filter in this case) and choose the drop down menu list for the "Filter Order" then I see all the scalars that are defined for vectors (e.g. min, max, etc) but I do not see the scalar that I defined manually.
Clicking on the "New scalar" button beside the "Filter Order" drop down and creating a new scalar creates a new scalar (seen in data manager) but does not allow it to be selected in the filter plugin. The number updates to the value of the newly created scalar, but it would be better to refer to it by name IMO.
The same applies for the "Cutoff frequency / Sample rate" scalar.
The same probably also applies for other plugins although I have not tried them.


Reproducible: Always



Expected Results:  
I would expect to be able to refer to scalars used in the filter settings by name, so that if I change one value it changes everywhere.
Comment 1 Netterfield 2013-09-24 20:51:15 UTC
Fixed in git master.