hpi-swa-lab / godot-pronto Goto Github PK

Here, the signal names are not shown entirely, but probably should be.

This screenshot was taken at 200% display scale.

The arguments for the connection function calls are crammed and tend to show scrollbars even when not necessary.

• add "Behavior" suffixes everywhere
• icons in docs

Options:

1. (preferred) detect that only one expression statement exists and use that. Challenge: we don't have a GDScript parser.
2. have a user interaction to allow multiple statements and default to assuming a single expression statement.

Here, the node connection window is active for a node near the right edge of main editor view. As a result, half of the window is not outside and thus inaccessible.

The window should always be fully visible.

Consider extending an existing behavior. ProgressBar control in Godot?

In particular: encapsulate logic required for dealing damage/headling, display.

Also consider other use cases.

Two reasons:

• The tween scheduling when many connections occur is not working well
• The editor reduces its framerate to 20fps on focus loss. We should lift this to 60 in ConnectionDebug.gd while the game is running.

Welche connection ist das problem wenn ein debugger kommt?

• failed dispatch of function
• what connection is responsible for which script? (#85)

Two scenarios:

1. Duplicating a node to "fork" it keeps references to the previous' nodes connections.
2. To be verified: "editable children" does now allow overwriting props of connections.

This is a limitation in Godot and sometimes even desirable (e.g. instances).

One possible solution could be to find other users of a connection in its edit dialog and show a "make unique" button if there's at least one other.

Quote from Slack:

ihr könntet in betracht ziehen für das grouping problem über eine StateMachine implementierung nachzudenken. die idee wäre also einen "AtRest"-State zu haben und einen "Moving"-State und jeweils bei deren "enter" oder "leave" signalen alle nötigen effekte auszulösen. zwischen states können benannte verbindungen vom user erstellt werden, die dann die transitions sind, etwa per trigger/function call oder per condition die busy gechecked wird. Könnte mir vorstellen, dass das ein guter erster schritt wäre sich langsam einer richtigen statemachine anzunähern.

• consider renaming it to "AutoGroup" and encapsulate the query criteria
• extend with new functions

For accessing via a name instead of a cumbersome get_node call. The criterium could be "closest child", eg. look for named state in children, if not found in parent's children, then in parent's parent's children, ...

In order to change the sequence of connections, we currently have to remove and recreate those connections.
(E.g. reorder some resetting state behavior to the front of a list is relatively costly.)

An overview of all connection, shown in the sidebar/inspector.

Maybe ct & pk?

Options:

• MouseCursor behavior
• Draggable/Droppable/Hover behavior
• Consider reuse of pickable property in Godot

We have a float value initially set to 2.5 with stepsize 0.5. However, when we start the game it shows a value of 3 inside the PrototypingUI (and this also seems to be the new value when the game has started). BUT we can still change the value with the slider to 2.5 during runtime.
Please try to fix this :)

e.g. I have an enemy with a NodeReady to reposition it. The spawner hides its child, thus from.get_root() return null

1. find scenarios that break and why, document these here
2. see if solutions can be devised

... if the placeholder has a Physics body parent. Because then, moving the placeholder will break the collision shape.

Add all your ideas as comments here

shortcut for opening list and move keyboard focus to a filter so that we never have to use the mouse again!

• Icons:

• query an API by a term?
• how to ensure a somewhat consistent style

• re-color
• API to add an outline color

Hint: please stay consistent where ever possible

Open question: how to select which child to spawn?

Suggestion: new method, otherwise always pick first

Use the connection debugger information to highlight connections in the editor that get activated.

• replaces only_once in timer
• allows repeating trigger of a connection

e.g., Spawner.scene_path

Possible solution: Generate corresponding script files in ignored folder

Some nodes like Bind allow defining code in the inspector. This is just a plain, one line text field, however. A better interface would be nice.

Two options:

1. We improve the way that the Prop resources are defined using a custom inspector.
2. We drop explicit dependencies entirely because it's easier to type out in the convert expression anyways using G.at or get_node (no more awkward value0/value1). Downside: we can visualize less because all info is hidden in the expression.

Maybe even link to docu