-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
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
Remote scene tree: Dock "Inspector" update problem #45205
Comments
Not limited to Windows nor beta. I am on 3.2.3 on Linux Manjaro and seeing the same behavior. |
Could the execution window be implemented in the editor? |
@Torguen: Been suggested already, requires an extensive rework of editor. |
Can you tell me the thread in which the suggestion was made? |
godotengine/godot-proposals#1864 (thread title is a bit different, but if you read through it, it'll point you to a PR which attempted the rework, and from there, you can probably find the original proposal from years back) |
Closing in favor of godotengine/godot-proposals#1864, as feature proposals are now tracked on the Godot proposals repository. |
Godot version:
3.2.4 beta 5 mono
OS/device including version:
win10 64
Issue description:
The inspector section does not update when "Remote" mode is automatically activated when executing a scene.
For the "Inspector" section to be updated, the user must select another node (this will minimize the execution window) and then select the initially selected node, this updates the "Inspector" dock, now the user must maximize the execution window again ... a good waste of time.
The "Inspector" dock could automatically update to show the selected node when the scene is run.
In this GIF you can see everything.
Steps to reproduce:
Enable "Remote" mode execution by default when executing a scene.
Select a node before running the scene.
Run the scene.
The "Inspector" dock appears empty or shows a node that is out of remote mode although you can see that a node is selected.
Minimal reproduction project:
The text was updated successfully, but these errors were encountered: