Re: Feedback
Reply #3 –
@Frenzie, not so hard by itself, we need to store time of last access per tab, which could be reused for one extra feature anyway.
But there are some additional complications (to avoid all possible issues to be expected from built-in behavior of QTabBar), we need to redo WindowsManager (preferably by replacing it by model describing entire session) which needs to be decoupled from TabBarWidget (which is also needed to properly finish customizable toolbars, so there could be no tab bar at all, not just hiding it) but we need custom tab bar to take advantage of such model. :-D
The above has to be done in next five months as it is one of the most important things for 1.0 (custom tab bar etc.).
We can have LRU switching earlier, but it may end up being out of sync with tab bar itself (noticeable at least when closing tab, as it may end up switching to wrong one).