Add set_value_no_signal() to Range
This commit is contained in:
parent
c29fe310f1
commit
4aa1efb0fe
4 changed files with 23 additions and 10 deletions
|
|
@ -16,6 +16,13 @@
|
|||
Called when the [Range]'s value is changed (following the same conditions as [signal value_changed]).
|
||||
</description>
|
||||
</method>
|
||||
<method name="set_value_no_signal">
|
||||
<return type="void" />
|
||||
<param index="0" name="value" type="float" />
|
||||
<description>
|
||||
Sets the [Range]'s current value to the specified [param value], without emitting the [signal value_changed] signal.
|
||||
</description>
|
||||
</method>
|
||||
<method name="share">
|
||||
<return type="void" />
|
||||
<param index="0" name="with" type="Node" />
|
||||
|
|
@ -59,7 +66,7 @@
|
|||
If greater than 0, [code]value[/code] will always be rounded to a multiple of [code]step[/code]. If [code]rounded[/code] is also [code]true[/code], [code]value[/code] will first be rounded to a multiple of [code]step[/code] then rounded to the nearest integer.
|
||||
</member>
|
||||
<member name="value" type="float" setter="set_value" getter="get_value">
|
||||
Range's current value.
|
||||
Range's current value. Changing this property (even via code) will trigger [signal value_changed] signal. Use [method set_value_no_signal] if you want to avoid it.
|
||||
</member>
|
||||
</members>
|
||||
<signals>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue