From 4aa1efb0febd0256931b36b51bc223a130995dc7 Mon Sep 17 00:00:00 2001
From: kobewi <kobewi4e@gmail.com>
Date: Mon, 31 Oct 2022 23:12:53 +0100
Subject: Add set_value_no_signal() to Range

---
 doc/classes/Range.xml | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

(limited to 'doc/classes')

diff --git a/doc/classes/Range.xml b/doc/classes/Range.xml
index 16e6e86f9e..9764318ee4 100644
--- a/doc/classes/Range.xml
+++ b/doc/classes/Range.xml
@@ -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>
-- 
cgit v1.2.3