Updating threshold limits in stripcharts

[Bob Watzlavick]

One of our users noticed that the stripchart thresholds weren't
correct after they updated their derived parameters. I did some tests
and it looks like the stripchart thresholds don't automatically update
if the thresholds for the parameter are updated. Redropping the
parameter seems to update the stripchart but our user was hoping the
stripcharts would pick up the change automatically. Is this by design
to protect the stripchart thresholds from inadvertent changes? Or is
it because parameter attributes only get propagated to the control
when it is dropped?

Thanks,
-Bob

[Michael Jones]

Bob, which method for changing the thresholds is being used?

A) 'hidden' ActiveX style property sheet
or
B) SetAThreshRangeMax(param, aT), SetAThreshRangeMin(param, aT),
SetWThreshRangeMax(param, wT), SetWThreshRangeMin(param, wT), Directly
in the derived equation for the parameter driving the stripchart


On Nov 2, 11:37 am, Bob Watzlavick <robert.l.watzlav...@lmco.com>
wrote:

[James Bretz]

Hi Bob,

Originally (as spec'd by the initial requirements from the FTEs), it was
designed to protect the settings in the display. Within that context, the
settings in the ParameterDefaults were just "default" setting for the
displays that were only applied to the display upon parameter drop. In other
words, they didn't automatically update the display based on changes to the
PD table.

Over the years we have deviated from this original requirement and deemed
some column values "global". These global properties actually do update
within the display upon every desktop load. Here's the list of global
properties:

("ParamType,ParamGroup,ParamSubGroup,ShortName,LongName,Units,DataSourceType,DataSourceArguement,UpdateRate,LLNegative,LLPositive,WildPointRangeMin,WildPointRangeMax,WildPointCorMethod,WildPointCorValue,SignChange,NullCorrection,NullBaseline,NullAverage,NullBias,NullGroup,SpikeDetectionMethod,SpikeCorMethod,SpikeChangeLimit,StringLookupTable");

As you can see, it's nearly every column. In version 7.0, we're suppose to
re-evaluate this behavior once again. We'll either have to make this
behavior user configurable, or we'll have to use the PD settings for
everything but the most basic settings (as in Color, etc).

The information for the thesholds is stored in the ParametersSavedInDisplays
table, so I'm sure we can develop a script to apply the threshold settings
from the PD table into the displays. Just let us know.

Jim

[Watzlavick, Robert L]

Mike,
Jim answered my question but they're just setting the limits directly in the derived parameter fields. They aren't being updated dynamically.

-Bob

[Michael Jones]

Woops, my misunderstanding!

On Nov 2, 12:34 pm, "Watzlavick, Robert L"

> > -Bob- Hide quoted text -
>
> - Show quoted text -