we have already catched one bug and i still foresee different problematic
scenarios - one example - you are in fullscreen and call exit. again you cancel
this exit while having somehow set tabbar toggling. iirc fullscreen has no
memory about the visibility states - it just toggles. now whatsover you do -
either forget to show again or do automatical showing while user has set this
off for fullscreen etc - and you switched to wrong state. i havent looked in
the code to check these scenarios but i dont like we have to even considering
such things because the visual elegance of closing tabbars.
pavel
I did something less risky:
Log:
Revert r29532 and do something less risky.
Now, the tabs are closed in reverse order, which is aesthetically better.
Consequently, we have to open the files (read from the session file) also in
reverse order.
Vincent
