https://bugs.kde.org/show_bug.cgi?id=491861
Pedro V <voidpointertonull+bugskde...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |voidpointertonull+bugskdeor
| |g...@gmail.com
--- Comment #1 from Pedro V <voidpointertonull+bugskde...@gmail.com> ---
This is more of an unimplemented feature problem than a bug, so importance is
likely to be more appropriate as "wishlist".
Guess part of your wish is already granted, the "Save Position" keyboard
shortcut seems to dump the current state in general, although I haven't tested
it extensively with multiple tabs and various settings changes.
Apparently the same functionality is available in the menu as Window -> Save
Position too.
I'm generally supportive of the idea, but beware of corner cases: Krusader
explicitly supports multiple instances by default, and to avoid gambling with
the saved state, exit should either check the saved state, or it should
unconditionally do a save.
For example I rarely open a secondary Krusader when the primary one is busy
with some very long running I/O task, potentially being completely frozen due
to an unresponsive mount point. In this case I would be quite confused if I'd
exit from the secondary first, then from the primary, but I'd have the
secondary state saved just because the primary figured that the state didn't
change since the last auto save.
--
You are receiving this mail because:
You are watching all bug changes.
