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

Issue with editing dictionaries in the inspector in the remote scene tree #44903

Open
Tracked by #47369
addmix opened this issue Jan 4, 2021 · 4 comments
Open
Tracked by #47369

Comments

@addmix
Copy link
Contributor

addmix commented Jan 4, 2021

Godot version:
3.2.3 stable

OS/device including version:
Windows 10 x64

Issue description:
Vectors, Dictionaries, etc. can't be edited during runtime when placed inside a dictionary whether or not the dictionary has the export keyword

Steps to reproduce:
create a dictionary with a vector, dictionary, or array inside. Make sure the dictionary has the export keyword so it is visible in the editor, during runtime, switch to remote, select the node, open the dictionary, and attempt to edit any of the values

Minimal reproduction project:
vector3dictionarybug.zip

@Calinou Calinou changed the title Issue with editing dictionaries in the inspector during runtime Issue with editing dictionaries in the inspector in the remote scene tree Jan 4, 2021
@amoriqbal
Copy link
Contributor

I can confirm this on Linux Mint 20.04. Godot 3.2.3.
As soon as we focus a field in the dict for editing, it automatically goes out of focus

@YuriSizov
Copy link
Contributor

Isn't this the same as #25375?

@amoriqbal
Copy link
Contributor

Isn't this the same as #25375?

Does not seem so! This issue (#44903) is independent of the level of nesting.

@YuriSizov
Copy link
Contributor

YuriSizov commented Jan 6, 2021

Does not seem so! This issue (#44903) is independent of the level of nesting.

The other issue doesn't have anything to do with nesting either. As you can see from my research #25375 (comment), it's all about constant updates for Dictionaries due to them not being properly comparable. You've deduced the same for your PR here.

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

5 participants