Calltree ordering is not always true #5
Description
The ordering in the calltree depends on the location at which each node is in the source code. This makes it convenient to keep a pattern that follows the source-code style. This is useful for visualising code when there is a lot of if-statements, as a way of ensuring some synchronisation between the calltree visuals and the source code visuals. However, currently a problem occurs when the source code looks like this:
func_one_call(
arg1_as_func_call(),
arg2_as_func_call());
In this case, the current visualiser will show arg1_as_func_call and arg2_as_func_call as happening after func_one_call. We should improve the calltree visuals to show take both control-flow and source-code layout into account