Skip to content

Commit

Permalink
Merge pull request #79656 from josefalanga/master
Browse files Browse the repository at this point in the history
Clarify when the `changed` signal is emitted for `Resource` and `Material`
  • Loading branch information
YuriSizov committed Jul 24, 2023
2 parents 9a7d8dc + bf62fb0 commit 9199649
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
2 changes: 1 addition & 1 deletion doc/classes/Resource.xml
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@
<method name="emit_changed">
<return type="void" />
<description>
Emits the [signal changed] signal. This method is called automatically for built-in resources.
Emits the [signal changed] signal. This method is called automatically for some built-in resources.
[b]Note:[/b] For custom resources, it's recommended to call this method whenever a meaningful change occurs, such as a modified property. This ensures that custom [Object]s depending on the resource are properly updated.
[codeblock]
var damage:
Expand Down
1 change: 1 addition & 0 deletions doc/classes/ShaderMaterial.xml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@
</brief_description>
<description>
A material that uses a custom [Shader] program to render either items to screen or process particles. You can create multiple materials for the same shader but configure different values for the uniforms defined in the shader.
[b]Note:[/b] For performance reasons the [signal Resource.changed] signal is only emitted when the [member Resource.resource_name] is changed. Only in editor, is also emitted for [member shader] changes.
</description>
<tutorials>
<link title="Shaders documentation index">$DOCS_URL/tutorials/shaders/index.html</link>
Expand Down

0 comments on commit 9199649

Please sign in to comment.