Hi guys,
my daily bug report.
If i copy and paste or duplicate nodes, the pasted or duplicated ones are not selected.
2 Likes
Related (Same?):
1 Like
@bjoern Not related to z sorting
Please always mention the vvvversion number with such bug-reports.I’m afraid i cannot reproduce with latest preview 6.7-0155.
Well, the issue appeared patching in a big project with many documents and dependencies associated. The version was the preview released 30 days ago, sorry i can’t be more specific.
Ok, then… if it happens again make sure to have a look in the Log and see if you see an error showing up there.
If i remember well, console didn’t say anything. I’ll inform if i see it again.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
Came across this problem in 7.0 again/still.
It seems to indeed be related to other projects/patches being open in the same editor instance.
The bug doesn’t surface for me with only an empty patch open, but it does happen in an empty patch when a bigger project is open in the editor at the same time.
What happens then is this - this happens while the project is running in parallel:
The IOBox is being duplicated with Ctrl+D.
You can see the IOBox being duplicated with the selected state briefly, then it disappears and pops up unselected again.
The gray Building Symbols bar is showing for a moment, which doesn’t happen if the project isn’t running in parallel.
If I close the project, the issue remains in the editor instance however. There’s no other files open:
What I did notice however, even though I closed the application patch of the other project, the Application patches of all previously loaded dependencies of the other project remain open?
At least this would explain while it still happens after closing the project.
Seems also a similar topic / issue like Copy/Pasting and Duplicating is sloppy?
Yes, for sure, also had to think of this one. Looks very much alike.
I can share the patch in private later, so you have a way to reproduce.
Should be fixed in upcoming. Reason for this behavior was that the package compiler did not remember that a particular package already failed to compile. So whenever it was triggered by certain user actions it caused quite some mayhem internally.
Oh and thanks @readme for sharing a reproducible test case.
3 Likes