Should we also move JumpManager, navBack and navForward to TabsController ?

I think we can make it independent: new class (JumpsController?) to listen tabs changes and code jumps with ITabsStatesListener, record these jumps into JumpManager, and on back/forward actions calls TabsController methods. One downside here is that we need to use currentPosition() from TabbedPane to save jump origin, but current position is tied to editor actually not to tabs, so it is already weird to have such method in TabbedPane 🤣 So maybe we can move this method to new JumpsController 🤔

(added NavigationController in last commit, sorry for wrong commit message)

Anything else that needs refactoring ?

Anything else that needs refactoring ?

No, I think all good now.
I will review and test current changes (maybe tomorrow, actually) and we can merge this PR.

I think all good now

And next I trigger some error without exception and spend lots of time debugging it 🤣
Exception was lost in the threads of background executor, adding more try/catch helps to reveal it (fix in de26dc9).
Anyway, I made some changes:

• use of default methods in ITabStatesListener helps to reduce empty methods in implementations
• make NavigationController listen tabs events, so it is really independent now
• move code of "sync with editor" feature into separate class
• add LogTabStates class to debug tab states events (helps understand order of similar action like select, open, codejump)
• another attempt to impove onTabsReorder
• resolve some NPEs
• resolve merge conflict

@Mino260806 please check my changes, I think we can merge this PR 🙂

@Mino260806 I will merge this PR. It contains a lot of good changes and fixes.

Sorry I had no time to check it