Just updated to burst 1.8.0 and noticed that in the burst inspector there’s an offset applied to the horizontal scroll bar (as seen in the picture) each time I click a new job. It doesn’t start all the way to the left as it did previously.
The offset was added intentionally as jobs can end up having a large amount of branches, pushing the code rightwards; meaning focus of the inspector ended up being on branch arrows instead of code.
So hopefully no code is cutoff by the offset, and branch end-arrows are still visible? If it’s hiding code, what font sizes/resolution does it happen for?
Right, I can see that argument. For me though, the overview and navigation benefits that the jump arrows give kind of disappear when they are cut off like that. I lose the “jump scope/indentation” information if that makes sense. Like what are “overarching” jumps (loops) here and what are smaller “inner” jumps (small if statements), what jumps can I ignore because they obviously go off the page vs what jumps are local etc. The arrows themselves and what color they have aren’t as easy to spot because they take up less screen space, and it’s more difficult to see if you have multiple arrows of different colors going to the same place and overlapping with each other, which also happens more with “branchy” code.
I’m not trying to be overly critical/negative here. I see what this feature is trying to do, but for me and the way I work with the burst inspector, it misses the mark and adds some extra clicks each time I’m accessing the compiled code in the inspector. Having some way to toggle it off would be really great for me 
That is definitely good feedback, thanks!
I’ll log a task for it, and have a go at it with your remarks in mind
Bump, Any news on this?
So we changed the logic behind the automatic horizontal scroll, so that it will only happen if the branch-markers fill >½ the inspector view.
The change should be in the next release of burst (1.8.3)
