obs-filters: Use double-precision where viable
We're expecting a variable with double precision. Since we don't read the value of these doubles with a particular precision, it can often lead to unpredictable results where the value set isn't the one intended due to the loss of precision from float->double conversion.
This commit is contained in:
committed by
Zachary Lund
parent
834ebbd2d4
commit
698e6418ba
@@ -121,10 +121,10 @@ static obs_properties_t *scroll_filter_properties(void *data)
|
||||
|
||||
obs_properties_add_float_slider(props, "speed_x",
|
||||
obs_module_text("ScrollFilter.SpeedX"),
|
||||
-500.0f, 500.0f, 1.0f);
|
||||
-500.0, 500.0, 1.0);
|
||||
obs_properties_add_float_slider(props, "speed_y",
|
||||
obs_module_text("ScrollFilter.SpeedY"),
|
||||
-500.0f, 500.0f, 1.0f);
|
||||
-500.0, 500.0, 1.0);
|
||||
|
||||
p = obs_properties_add_bool(props, "limit_cx",
|
||||
obs_module_text("ScrollFilter.LimitWidth"));
|
||||
|
Reference in New Issue
Block a user