Version: (using KDE 3.5.9) Installed from: SuSE RPMs [ Sorry for posting this for kdelibs but I have no idea where to put this issue ] The problem is this -- such apps as Konqueror, Konsole, KDevelop, Kile uses the same tabs mechanism. But it is up to those apps what will happen when you close the app. Will previously seen be activated? Left? Right? When you switch from app to app it is common to make a mistake because behaviour is different. It would be good to set this for KDE once for good and work in peace. Btw. another report about unification need: https://bugs.kde.org/show_bug.cgi?id=80657
this can't be fixed in the tabwidget, as that one doesn't know _anything_ about the content of the tabs. You need to file bugreports with all the apps individually, those are responsible for storing the information about the content of each tab in a way to restore it.
> this can't be fixed in the tabwidget, as that one doesn't know _anything_ > about the content of the tabs Andreas, what content? Content here is irrelevant -- only the fact the tab _was_ closed (so there is no content). Btw. when I press globally defined shortcut ctrl+tab (jump to next tab) then kdelibs does the switch or the app? I am asking for KDE-wide policy: on close skip to next, previous, last_seen That's it (oh, well, plus some configuration in Kcontrol? to set it properly). If KDE (kdelibs) is able to make this jump fine, if not -- fine too. > you need to file bugreports with all the apps individually This is impossible -- what is the point of having global KDE policy if I have to ask each app developers to provide configuration for such policy. It is contradiction (global is not local). The whole point is to set it (just policy) in one place, and use it everywhere. But true -- if some app disobeys this global policy that I should write a report for each app. Reopening -- it is about providing policy, and setting in one place, not about executing such policy (but it would be a plus of course if it would be possible).
I think defining which tab is active after you close one can be a global setting, but...afaik it actually is, just that some apps want to change this behavior and they can change it, because it is allowed. So somewhat both of you are right, this is inconsistent, but this is up to the apps to do it "right".
Apparently the "close the app" (which was a typo) made me think you're talking about re-opening the tabs in the same order when restarting the application. Andras: You're right, there is already API to select that, but I don't think there's a global setting for that. At least KTabBar doesn't read anything from any configuration.
Andreas, sorry for the typo, I meant "close the tab". Andras, I was hoping not only for reading some hardcoded policy but setting it (by user) too.
On Tuesday 06 May 2008, Andreas Pakulat wrote: > Andras: You're right, there is already API to select that, but I > don't think there's a global setting for that. At least KTabBar > doesn't read anything from any configuration. I meant that there is a global, default behavior. :) Somehow I think in this case it doesn't make sense to have a configurable default, maybe it would be nice to see what the apps are using now and come up with a (hardcoded) default that fits their needs. At least having an UI for this doesn't really make sense. IMO, of course.
UI maybe not, but configurable by editing some config file. Why it is useful -- because you could configure it once, not X times. Why configurable at all? Because I would be not surprised that some people prefer "go to last seen" policy. Just in case :-) -- I opt for default "go to next tab" on close. Why? Because it is a good analogy to deleting items in listbox, to deleting lines in editor, etc.