Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When running the app show all current values in nodes #288

Open
GhostNr1 opened this issue Apr 23, 2024 · 2 comments
Open

When running the app show all current values in nodes #288

GhostNr1 opened this issue Apr 23, 2024 · 2 comments

Comments

@GhostNr1
Copy link

Description

When in debug mode it would be very beneficial to see all the current values in one or many nodes instead of drag out a print node just to see what the values are when you are running.

Implementation ideas

No response

@Naros
Copy link
Member

Naros commented Apr 25, 2024

Hi @GhostNr1, thinking on this some, I wonder if using the concept of watches makes sense here.

For example, if you want to capture and monitor the value of a node pin at runtime, you could right-click the pin, and there would be one of two options: "Watch this value" and "Stop watching this value".

When the pin is being watched, it is added to a "watches" panel in the debugger area of the Godot editor, where we can show the variable name and its value. As the orchestration runs, the watch panel updates in real-time, showing the current values. Given that two pins could have the same name, we may need to use a hierarchy for rendering:

+ OperatorNode_23
  + A: 25
  + B: 26
+ OperatorNode_24
  + A: 51

Regardless of how we render them, however, what do you think of this idea?

@GhostNr1
Copy link
Author

I think the idée that you watch and unwatch pins are very nice. If this approach are easier and faster to do as a first step I would be ok with it. But in the long run I think it would be much easier to follow if the number is in the graph and you can see it next to the pin instead of looking in the list.

It can be tricky as you say to show what node is displayed in the watch list compared to have it just next to the pin.

But start to do the watch in the list and then maybe build on that later on?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants