tutorials/scripting/gdscript/gdscript_basics

[giscus[bot]]

tutorials/scripting/gdscript/gdscript_basics

GDScript is a high-level, object-oriented, imperative, and gradually typed programming language built for Godot. It uses an indentation-based syntax similar to languages like Python. Its goal is to...

https://docs.godotengine.org/en/stable/tutorials/scripting/gdscript/gdscript_basics.html

[mccolljr]

Is there a concept of "generators" in gdscript? For example:

for obj in compute_a_long_list():
    do_something(obj)

func compute_a_long_list():
    # in c# it would be yield return 1
    # yield return obj1
    # yield return obj2
    # etc...

[Calinou]

GDScript supports custom iterators, but I don't know if that's the same as generators.

[enetheru]

4.3 introduced PackedVector4

[Calinou]

• Fixed in Document PackedVector4Array godot-docs#9865.

[Marenz]

Is there a way to use await with signals that have parameters, as in, get access to them?
e.g.:

signal user_ready(id: int)
signal user_changed_color(id: int, color: Color)
func foo():
    await user_ready # no access to id?
    await user_changed_color # Access to id & color?    

[nonchip]

await returns the only argument or array of arguments, so this should work:

signal user_ready(id: int)
signal user_changed_color(id: int, color: Color)
func foo():
    var id: int = await user_ready
func bar():
    var params: Array = await user_changed_color
    var id:     int   = params[0]
    var color:  Color = params[1]

wish we had destructuring assignment for cases like that. imagine just being able to do var [id: int, color: Color] = await user_changed_color!

also this seems mentioned nowhere in the docs, had to dig my way all the way through the compiler source to find confirmation: https://github.com/godotengine/godot/blob/e4e024ab88efe74677769395886bc1b09eccbac7/modules/gdscript/gdscript_function.cpp#L137

also note that signals can be called with an arbitrary amount of arguments, the declaration is mostly for doc purposes, as you can see by Signal not even knowing about it, so what it returns gets decided at the time of the signal being handled, which can be quite "fun" (yknow, not "haha-funny" but the other kind) depending on your situation...

[Lazy-Rabbit-2001]

Since typed dictionaries are introduced in 4.4, a new section similar to "Typed Arrays" should be added for "Dictionary" section.
Meanwhile, @icon can be also used for unnamed scripts and works as usual, which I think should be noted, too.

[Calinou]

Does the icon show up anywhere if you use @icon on a script without a class_name?

[Lazy-Rabbit-2001]

yes, you can have a try, especially opening its document if you have any documental comment in the script with no class_name, where you will see its custom icon at the top of the page of its document

[Calinou]

Meanwhile, @icon can be also used for unnamed scripts and works as usual, which I think should be noted, too.

Reading the page again, I think this is already stated above:

# (optional) icon to show in the editor dialogs:
@icon("res://path/to/optional/icon.svg")

There's no implication that you have to use class_name along with it.

[7ombie]

I'm just learning GDScript now, and didn't infer anything like that either.

[Gonderage]

On property getters, does a property run its getter each time the property appears, or is the property's calculation cached?

Silly example:

var my_var : int:
     get = expensive_function

func expensive_function():
    # Does a lot of stuff

func my_function():
    var new_int := 0
    for x in big_number:
        new_int += my_var      # does this call the getter each time?
        new_int += my_var + 1  # or is it cached for future lines?
        new_int += my_var + 2
    return new_int

[Gonderage]

Also, if a property is used in the getter itself, does it recursively call its getter? Example I'm working on right now:

var direction : Vector2: get = get_direction
signal just_moved

func get_direction() -> Vector2:
	var vector := Input.get_vector("move_left","move_right","move_up","move_down")
	var rotation : float = get_window().get_camera_3d().global_rotation.y
	# To check if I just started moving, I need to
	# know the direction from the previous input.
	if direction.length_squared() > 0.1 and vector.length_squared() < 0.1:
		just_moved.emit()
	return vector.rotated(-rotation)

[Gonderage]

nvm the second one, i just reread that getters dont recursively call themselves

[GeminiSquishGames]

On the warning about lambdas, is the third code block not just repeating the second, failing to actually represent the difference in variants outside of the lambda's scope that are pass-by-reference data types?