Tagged with #godot

5 results found.

• Sander March 31, 2025 at 11:36 pm

  OK I figured out a very useful #Godot debugging trick: conditional breakpoints are not supported natively but can be added to your code.

  1. Set an if statement for the condition or expression you want to break on.
  2. As the code block for the condition being true add pass and set a breakpoint on this line.
  3. After hitting it, all the debugging tools are available.
• Sander March 29, 2025 at 5:12 pm

  #til In #Godot when you attach a node with a scale as a child of one that doesn't support scale (Node vs Node2D for example), there is a flicker as the card is rescaled. Convert the node to a scale supporting type to fix this.

• Sander March 5, 2025 at 9:35 am

  #til In Godot, if a scene is instantiated at design time and a child is added to it, does the child belongs to the scene whose tree is currently open, or the scene it's attached to?

  When duplicating a node (including a scene) at runtime it is the node tree where the node sits that is duplicated, so it includes the child. But if the scene is marked as a InstancePlaceholder, and create_instance() is called at runtime, it creates a instance of the scene, and any attached children have to be duplicated and attached to the instance with code. #Godot

• Sander March 1, 2025 at 12:19 pm

  #til In Godot, when you have a project containing a node MyNode that is a scene itself, and MyNode contains two child nodes within the scene and one is added as a child of MyNode in the project, the number of get_children() that a script belonging to the root node of the MyNode scene returns is 3. #godot

  

  

• Godot simplified drag n drop tutorial

  Sander March 18, 2023 at 12:06 am

  I was "following" Generalist Programmer's Godot drag and drop tutorial and I made a few refinements that I wanted to share. Please read the tutorial and then follow along.

  Drop-in behaviour

  Wouldn't it be cool to give a node drag and drop behaviour simply by dropping in a node with the script, independent of any other scripting?

  We can do this by creating a new child node (here called Drag-and-drop Dropin), and attaching the script to it. It must extend from the dropin Node2D.

  

  In the script itself we make two changes:

  1. Disconnect the KinematicBody2D's input_event signal, and write it in code in the dropin's _ready function. Call it on it's parent: get_parent().connect("input_event", self, "_on_KinematicBody2D_input_event"). We want to process the input_event of the KinematicBody2D, not the dropin.
  2. In the _process function, assign the mouse position to the parent of the dropin: get_parent().position = Vector2(mousepos.x, mousepos.y).
  3. Same for the last line in the script where we set the position of the parent.

  The script then reads as follows:

  extends Node2D
  
  var dragging = false
  
  signal dragsignal
  
  
  func _ready():
      connect("dragsignal", self, "_set_drag_pc")
      get_parent().connect("input_event", self, "_on_KinematicBody2D_input_event")
  
  
  func _process(delta):
      if dragging:
          var mousepos = get_viewport().get_mouse_position()
          get_parent().position = Vector2(mousepos.x, mousepos.y)
  
  
  func _set_drag_pc():
      dragging = !dragging
  
  
  func _on_KinematicBody2D_input_event(viewport, event, shape_idx):
      if event is InputEventMouseButton:
          if event.button_index == BUTTON_LEFT and event.pressed:
              emit_signal("dragsignal")
          elif event.button_index == BUTTON_LEFT and !event.pressed:
              emit_signal("dragsignal")
      elif event is InputEventScreenTouch:
          if event.pressed and event.get_index() == 0:
              get_parent().position = event.get_position()
  

  Simplifying the script

  I was refactoring this, and it turns out we can simplify this further.

  1. We don't need a dragsignal because the signal is both emitted and consumed within the same script. We can just replace the emit_signal calls with calls to _set_drag_pc(). We can then remove the connect() call in the _ready function, and the signal dragsignal.
  2. The same function is called when the left mouse button is both pressed and not pressed, so we can remove that conditional and remove the elif statement in the input event handler.
  3. As there is only one invocation of _set_drag_pc() we can inline it.

  The final script becomes:

  extends Node2D
  
  var dragging = false
  
  
  func _ready():
      get_parent().connect("input_event", self, "_on_KinematicBody2D_input_event")
  
  
  func _process(delta):
      if dragging:
          var mousepos = get_viewport().get_mouse_position()
          get_parent().position = Vector2(mousepos.x, mousepos.y)
  
  
  func _on_KinematicBody2D_input_event(viewport, event, shape_idx):
      if event is InputEventMouseButton:
          if event.button_index == BUTTON_LEFT:
              dragging = !dragging
      elif event is InputEventScreenTouch:
          if event.pressed and event.get_index() == 0:
              get_parent().position = event.get_position()
  

  So this dropin can now be added to any node to add Drag-and-Drop behaviour. I think the script can be improved a little so that the node is not centered under the mouse cursor but takes account the offset where it is picked up.

  Let me know your thoughts! #godot