-
-
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
Rework update_property
for array
#80706
Rework update_property
for array
#80706
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You also need to rebase, your branch is far far behind, about a month and a half
update_property
for array.
a52b26b
to
132860f
Compare
Just realised I forgot to tell. This fix only the array part of the issue linked and not the dictionary part I will deal with dictionnaries with my rework of the dictionary editor. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested locally (rebased on top of master
6758a7f), it works as expected (including on multi-page arrays).
Note that an issue that causes the entire array's contents to disappear (including in the saved data) still occurs if you happen to right-click the area on the left between the drag-and-drop icon and the property name then choose Paste Value.
Was that happening before my PR or was it something introduced with this? |
It's not introduced by the PR, I can reproduce it in It's a separate issue and can be fixed in a separate PR. |
update_property
for array.update_property
for array
132860f
to
0d0b401
Compare
Dragging array elements may make the cursor disappear permanently. Changing array type in code (in this case from Resource to Node) results in this error
You can't assign anything until reloading the scene. |
This is something already present in master. When testing my own PR I stumbled upon it too. The problem on the back end that it can still hold an array that is not of the right type. Normally returning to default is enough to fix it which is a bit less tenuous then re opening the scene. |
I'm not sure about this one but it seems like it was present before my PR. But I'm not sure I'm looking at the same that causes the mouse to fully disappear. Mine is to focus ones of the button to drag element and then long press enter. |
0d0b401
to
b42a48e
Compare
It's worse after the last update xd @export var array: Array[int] Change array size to 21, you'll get spammed with
and the editor crashes when you unselect the node:
|
b42a48e
to
a8e21ac
Compare
I reversed the |
I did more testing to the disappearing mouse bug (using Windows) and it seems to be introduced by this PR. YxigaWlelf.mp4I can drag as much as I want and nothing happens. U6y499hKJJ.mp4It breaks after a few drags, consistently. |
a8e21ac
to
029e359
Compare
I finally took the time to look at what was happenning with what kobewi reported. It was simply that in some condition I was deleting the slot that was being dragged around. I also added AThousandShips improvement. |
e07cdb0
to
53ba4e1
Compare
Apply suggestions from code review Co-Authored-By: Tomek <kobewi4e@gmail.com>
53ba4e1
to
b4d96bc
Compare
Thanks! |
Fixes #75124
This is a huge rework of how array property editor is updated. Previously it would delete every editor for each element and recreate them. Now it first check whether the property editor will be the same.
This is not 100% tested but I couldn't find other bugs so decided to share to see if other people could find some bugs while I'm finishing testing otr if they had any suggestion on the code