[FEATURE REQUEST] [Blueprint] Larger snap area of node inputs

[Slavq]

Dragging wires is a natural part of Blueprint workflow Sometimes when i want to quickly drag wire off an output, or connect it to an input, i just miss - and insted of connecting wire to input, Blueprint thinks that i want to place a new node.



How about inserting some little magnet inside every input? It would help snapping wire when it's really close. This snapping would not be visible when dragging a wire (imho it would just annoy like that), but only when releasing it. Well, actually the image above is enough to illustrate this little idea

[John Alcatraz]

yeah you are right, would be nice

[KITATUS]

How about a simple dialog box (Like with the variable "Get" and "Set"). If you're in the vicinity but miss the node input, it could say "Connect" or "New Node"?

[Adam Davis]

Hi Slavq,

Thank you for your request, we will take this into consideration.

[Slavq]

Today i've worked in blueprints with touchpad (on laptop) and... I missed these inputs many times, which was very annoying But even with mouse it's still a problem when i work fast.
That's almost 3 months from this request, any news?

[asperatology]

Expect this to be in 4.8, I think.

[Slavq]

... I still often miss inputs when trying to work fast with blueprints Maybe 4.9?

[MaFloBra]

definitely +1

[Azarus]

I already mentioned this months ago, no one seemed to care until now. Please at least give us an option to increase the size of the pins!

[Chosker]

for sure, +1

also would be nice if they make it bigger for dragging out a new connection from an output pin. there's a bug that the 'highlight area' and the 'actual dragging area' are not the same (highlight area is bigger). so many times the thing highlights, but instead of making a new connection you end up moving the whole bp node :/

[CriErr]

its can be even like that

[Dannyk90]

its can be even like that
[ATTACH=CONFIG]54552[/ATTACH]

yeah CriErr has my idea too!

[Slavq]

^ This could cause some problems when two nodes would be close to each other (output snap area of Node1 overlaps input snap area of Node2) - but anyway yeah, in this case bigger = better

[CriErr]

^ This could cause some problems when two nodes would be close to each other (output snap area of Node1 overlaps input snap area of Node2) - but anyway yeah, in this case bigger = better

make z order priority for output

[Slavq]

make z order priority for output [ATTACH=CONFIG]54560[/ATTACH]

User can also want to change input pins, and it would be overlapped by output then :P