There is a cosmetic bug, when I drag connection from one node to another it look like I am pointing on a connection node, but editor thinks that I am pointing on an empty space - it seems like connection hot zones are misaligned a little bit.
Look at the screenshot - upper screen I am pointing on the center of a |> node, but no connection is handled. If I move pointer alittle lower, than at handles the connection - the lower screen.
Hi ,
I don’t know if it’s because I’m using 4.9.1, but I was not able to reproduce this issue. Please try updating the engine and let me know if it does or does not rectify the issue. -Thanks
Hi ,
I am using source build 4.9.1. I don’t think my changes interfered with blueprint editor. I think this bug usually appear after some time of blueprint editing. It is not an always reproducible bug. But I think zooming, scrolling, opening different blueprints can reproduce it.
I had noticed it from 4.8 version. I am usually dragging and dropping connections really fast, so this bug leads to the creating of new nodes instead of connecting them. So you can try doing the same - edit a lot of blueprints for some time, maybe some copy and pasting should be done.
If you can tell me where in code the position is handled I think I can debug it and search for some clues.
After creating a lot of repeat nodes, I was able to recreate this but only if zoomed to a certain positon. If zoomed all the way in, this issue does not occur for me. Do you find this is the case as well? Let me know the circumstances where you encounter this and I’ll enter a bug report.
(I’m working on locating where the code resides for handling this positioning).
Hello ,
Don’t think it is zoom related. I think all nodes without upper title are affected. If |> node is placed without upper title, in the rounded zone of the block, then hot zone is not handled. Like the upper rounded zone is blocking it.
Hi ,
It turns out that the comment bubble, although hidden, is blocking you (and other users) from making the connection normally. I have entered this as a bug: UE-21225. When this has been fixed, we will notify you with an update to this post.
Thanks for pointing this out and helping to improve UE4!
Good to hear that you managed to find the source of this bug. Unreal Engine is cool and should be better with every release. I am happy to be the part of this process )
This has been reported fixed in the following CL:2698488. Thanks again for reporting this issue.
