Few Minor UI Bugs

[ConnorNelson]

Issue 1
Here is what happens:

1. Open some project (e.g. https://cloud.binary.ninja/bn/04ad9924-0507-43d5-8cb6-0cec33122587).
2. Double click on the main function on the left bar to start analyzing main.
3. Click in the background of the CFG view.
4. Press space to switch to the Linear Disassembly view.

Rather than bring me to the linear disassembly for main, it brings me to struct Elf64_Header __elf_header and beyond (probably whatever the default location is for the project).
Interestingly, if I manually click on "Linear Disassembly" at the top, it correctly brings me to main (as long as the address param is still set within the url, which it isn't after I hit space).
Further, if I click on the main symbol within the CFG or on one of the instructions before hitting space, it brings me to the correct location within the Linear Disassembly view.

Issue 2
When I click (or double click) on a function, or an instruction within a function while in the Linear Disassembly view, I would expect my function context to switch. By this I mean, I would expect that the function param within the url would change, the function name would become blue on the left bar, and when hitting space to go to the CFG view, I would be brought to that function/instruction. Instead, none of these change and I am brought to whatever my previous function context was.

Issue 3
"Show variable types at top of function" doesn't seem to affect Disassembly, LLIL, MLIL while in the Linear Disassembly view. It only affects HLIL. Otherwise, the variables and their types are always shown.

Issue 4
If I scroll while in the Linear Disassembly view, and I want to quickly get back to a particular function, I cannot double click that function in the left side bar. I must instead double click a difference function, and then double click the function I am interested in.

Issue 5
Sometimes when scrolling/clicking through the Linear Disassembly view, when I press i in order to change IL, the view is brought to the default location (e.g. struct Elf64_Header __elf_header). It's not super easy to track down under what exact conditions this occurs.

Not any major issues, but I figured I'd document these minor issues.

[xavierholt]

Issue 4 got fixed as part of #133.