https://bugs.kde.org/show_bug.cgi?id=440663
--- Comment #87 from Andrey <butir...@gmail.com> --- (In reply to Steve Vialle from comment #85) > (In reply to Andrey from comment #83) > > As I wrote above, that "open new folders in tabs" option naming in dolphin > > just unfortunate and misleading. > "Open new folders in tabs" does exactly what it says on the tin - it causes > folders opened externally (e.g. from a desktop icon etc.) to open a new tab > in an existing dolphin window, rather than opening a new window. > That's what it's always done, since the introduction of dolphin as the > default file manager. It's not misleading, and it has only become > "unfortunate" with the introduction of this "focus archive" shenanegans. The name doesn't reflect the fact a new window will be opened shall the item is selected/opened externally in Dolphin with the option unchecked. That is misleading. > > If it UNchecked, it _guarantees_ the new Dolphin window will be opened > > instead of selecting the archive in current tab/new tab. > Well it does _now_. It sure didn't before all this started. If you can read the code, you can make sure I didn't touch the option, so it works as before. > > Please try to check that option and retest. > Checking "open new folders in tabs" does indeed prevent the spawning of new > dolphin windows on extraction. However, as above, it also causes externally > opened folders to open tabs rather than new windows. > For those of us used to a traditional desktop workflow, this is extremely > irritating. It is also logically unrelated to background archive operations. The option influences behavior both when an item is selected externally or it's an archive crated from Dolphin context menu, it wasn't touched. > I'm going to keep > patching out your changes locally until this doesn't steal focus, raise > windows, hijack existing options, or generally get in my way. Nor any other options were touched. > If you are determined to implement this feature, please provide a clearly > labelled option (a *new* option, not one with it's own well-established > uses) to disable it entirely. I didn't implement the feature, the feature was there. I just fixed it so it started to work for the context menu created archives at all (yes, it was there for them either). This probably is the source of confusion. -- You are receiving this mail because: You are watching all bug changes.
