Range: Properly bind value emitted by 'changed' signal

This was fixed in the `master` branch by removing the value in #29831,
but for `3.1` we preserve compatibility, even if redundant with
'value_changed'.

Fixes #35395.
This commit is contained in:
Rémi Verschelde 2020-01-21 09:25:07 +01:00
parent 513bfe496c
commit 227a81c119
2 changed files with 3 additions and 1 deletions

View File

@ -60,6 +60,8 @@
</members> </members>
<signals> <signals>
<signal name="changed"> <signal name="changed">
<argument index="0" name="value" type="float">
</argument>
<description> <description>
Emitted when [member min_value], [member max_value], [member page], or [member step] change. Emitted when [member min_value], [member max_value], [member page], or [member step] change.
</description> </description>

View File

@ -266,7 +266,7 @@ void Range::_bind_methods() {
ClassDB::bind_method(D_METHOD("unshare"), &Range::unshare); ClassDB::bind_method(D_METHOD("unshare"), &Range::unshare);
ADD_SIGNAL(MethodInfo("value_changed", PropertyInfo(Variant::REAL, "value"))); ADD_SIGNAL(MethodInfo("value_changed", PropertyInfo(Variant::REAL, "value")));
ADD_SIGNAL(MethodInfo("changed")); ADD_SIGNAL(MethodInfo("changed", PropertyInfo(Variant::REAL, "value")));
ADD_PROPERTY(PropertyInfo(Variant::REAL, "min_value"), "set_min", "get_min"); ADD_PROPERTY(PropertyInfo(Variant::REAL, "min_value"), "set_min", "get_min");
ADD_PROPERTY(PropertyInfo(Variant::REAL, "max_value"), "set_max", "get_max"); ADD_PROPERTY(PropertyInfo(Variant::REAL, "max_value"), "set_max", "get_max");