When navigating complex solutions in blueprint that involves many functions that branch, it is easy to get lost. Looking inside function F and opening a function node, it can be difficult just to get back to function F again. I often end up going back to function A and following the flow back to F rather than clicking on tiny tabs that can’t even hold a single symbol, sometimes closing them by accident because a few pixels of the close tab button is visible.
A simple “go to previous function” button would be super neat.
Maybe it could even store the last 10 or so functions you visited. How amazing wouldn’t that be!?
The problem is, that while walking down a Blueprint path (by clicking on function nodes for example) you are always redirected to another asset and/or another function, without any way to go back. When trying to find a variable or debugging an issue, after you found the low-level node you were looking for, you usually want to go back to the function with which you are actually working - sometimes with zero chance to find it ever again. You have no indication at all, out of the 10 open blueprints which one were you working with, and if you figure it out, then good luck finding the function you have been just 1 minute ago when there are probably 20 function tabs open.
Blueprints definitely and desperately need a “Go back” functionality, like in browsers. Nothing new, software in 1997 already knew this. It also shouldn’t be an excessive undertaking, we just need to store the asset/function in a stack upon navigating into it and pop it whenever Back is pressed.
