virtualx-engine/demos/2d/dynamic_collision_shapes/dynamic_colobjs.gd


extends Node2D

# Member variables
const EMIT_INTERVAL = 0.1
var timeout = EMIT_INTERVAL


func _process(delta):
	timeout -= delta
	if (timeout < 0):
		timeout = EMIT_INTERVAL
		var ball = preload("res://ball.tscn").instance()
		ball.set_pos(Vector2(randf()*get_viewport_rect().size.x, 0))
		add_child(ball)


func _ready():
	set_process(true)
Ability to keep collisionshapes and collisionpolygons when running the game. Works for 2D and 3D These are still just helpers in case you want to animate them or access them directly. Modifying the real shapes is still done via CollisionObject and CollisionObject2D APIs But an API was added so you can query which shapes from CollisionObject correspond to which CollisionShape. Have Fun! 2015-09-16 03:07:03 +02:00
			`extends Node2D`

Improve code formatting The scripts were streamlined using more or less the following conventions: - space after a comma in lists of arguments - spaces around weak operators (+, -), no spaces around strong operators (*, /) - spaces around comparison operators and compound assignment operators - space after a comment start (#) - removed trailing spaces or tabs, apart from those that delimit the function indentation level (those could be removed too but since they are added automatically by the editor when typing code, keeping them for now) - function blocks separate by two newlines - comment sentences start with an upper-case letter 2015-11-21 16:13:43 +01:00			`# Member variables`
			`const EMIT_INTERVAL = 0.1`
			`var timeout = EMIT_INTERVAL`

Ability to keep collisionshapes and collisionpolygons when running the game. Works for 2D and 3D These are still just helpers in case you want to animate them or access them directly. Modifying the real shapes is still done via CollisionObject and CollisionObject2D APIs But an API was added so you can query which shapes from CollisionObject correspond to which CollisionShape. Have Fun! 2015-09-16 03:07:03 +02:00
			`func _process(delta):`
Improve code formatting The scripts were streamlined using more or less the following conventions: - space after a comma in lists of arguments - spaces around weak operators (+, -), no spaces around strong operators (*, /) - spaces around comparison operators and compound assignment operators - space after a comment start (#) - removed trailing spaces or tabs, apart from those that delimit the function indentation level (those could be removed too but since they are added automatically by the editor when typing code, keeping them for now) - function blocks separate by two newlines - comment sentences start with an upper-case letter 2015-11-21 16:13:43 +01:00			`timeout -= delta`
			`if (timeout < 0):`
			`timeout = EMIT_INTERVAL`
Port 2D demos to TSCN/TRES formats Part of #4196. 2016-04-02 12:35:23 +02:00			`var ball = preload("res://ball.tscn").instance()`
Improve code formatting The scripts were streamlined using more or less the following conventions: - space after a comma in lists of arguments - spaces around weak operators (+, -), no spaces around strong operators (*, /) - spaces around comparison operators and compound assignment operators - space after a comment start (#) - removed trailing spaces or tabs, apart from those that delimit the function indentation level (those could be removed too but since they are added automatically by the editor when typing code, keeping them for now) - function blocks separate by two newlines - comment sentences start with an upper-case letter 2015-11-21 16:13:43 +01:00			`ball.set_pos(Vector2(randf()*get_viewport_rect().size.x, 0))`
Ability to keep collisionshapes and collisionpolygons when running the game. Works for 2D and 3D These are still just helpers in case you want to animate them or access them directly. Modifying the real shapes is still done via CollisionObject and CollisionObject2D APIs But an API was added so you can query which shapes from CollisionObject correspond to which CollisionShape. Have Fun! 2015-09-16 03:07:03 +02:00			`add_child(ball)`


Improve code formatting The scripts were streamlined using more or less the following conventions: - space after a comma in lists of arguments - spaces around weak operators (+, -), no spaces around strong operators (*, /) - spaces around comparison operators and compound assignment operators - space after a comment start (#) - removed trailing spaces or tabs, apart from those that delimit the function indentation level (those could be removed too but since they are added automatically by the editor when typing code, keeping them for now) - function blocks separate by two newlines - comment sentences start with an upper-case letter 2015-11-21 16:13:43 +01:00			`func _ready():`
			`set_process(true)`