┌   ┐
54
└   ┘

summaryrefslogtreecommitdiff
path: root/po/cs
diff options
context:
space:
mode:
authorStefano Crocco <[email protected]>2024-01-14 09:36:32 +0000
committerMéven Car <[email protected]>2024-01-14 09:36:32 +0000
commit0d01cb09c9ae4d3f208e7a3feca79b3c822deb1e (patch)
tree26e51b53e0999588e782a449b536f5bc7a8ed06d /po/cs
parent0d2aa8a1bed1cef4a2dd99493dacf40812807cf9 (diff)
Never emit the fileMiddleClickActivated signal if isTabsForFilesEnabled is true
Commit d27ee07d makes it impossible for applications embedding Dolphin part (for example, Konqueror) to react to middle mouse click on a file. If I understand correctly (I'm not familiar with Dolphin code) the `fileMiddleClickActivated` signal is connected with a slot in `DolphinViewContainer`, which is only used by Dolphin itself and not by `DolphinPart`. The result is that middle clicking on a file (except archives) from a Dolphin part has no effect. To avoid this situation, I removed the check for `!archiveProtocolIsEmpty()` in the `else if` condition. This way, if `isTabsForFilesEnabled()` is `true`, which should be true if and only if the view is inside a `DolphinPart`, the `activeTabRequested` or `tabRequested` signal will be emitted, allowing the embedding application to respond however it wants. When the view is inside the Dolphin application, instead, `isTabsForFilesEnabled()` will always be `false`, so the new behavior will be used.
Diffstat (limited to 'po/cs')
0 files changed, 0 insertions, 0 deletions