dolphin/src/tests, branch pixelated-scaling-optionPatched KDE Dolphin with Pixel Scaling
https://fiftyfourth.xyz/git/dolphin/atom?h=pixelated-scaling-option2026-02-21T08:37:12Zviewproperties: don't use intermediate tmp file to save viewprops2026-02-21T08:37:12ZMéven Carmeven@kde.org2025-11-29T10:08:46Zurn:sha1:8e4d7e1e2196425d54eefc65da096de20c509171Add keyboard anchor assignments to mouse events2026-01-21T09:01:28ZTomasz Kottomasz.kot13@gmail.com2025-11-28T15:11:00Zurn:sha1:843d10ae2ab6a7f2c6f69b63fa278fdd6162254c
The mouse events need to modify the keyboard anchor assignments as well,
because selecting an item with a mouse and then navigating with keyboard
wouldn't follow the same selection.
BUG: 508609
dolphinview: when creating a subfolder expand to it if in details mode2026-01-20T09:45:34ZMéven Carmeven@kde.org2025-11-16T12:53:58Zurn:sha1:93a6978655fc1ce9e0fd8ea08029859f71c32db9
So the new folder is in view.
viewproperties: remove temp file after loading defaultConfig2026-01-12T12:57:40ZSergey Katuninsulmpx60@yandex.ru2026-01-12T12:57:40Zurn:sha1:b9b06174afca99d7fe544940b950a7323631271a
It turns out that since f6c97d52220be9bd996b71309051e56ff7aa1834 a temp file is created here with each `save()` call for this default config, which is not deleted later. In another place where `defaultProperties()` is called for `m_node`, the file is deleted in the destructor of this class. But it is not deleted here.
So, remove temp file after loading defaultConfig or it will create temp file on each save() operation in /tmp folder.
Also keep the global/.directory file when xattr isn't supported.
BUG: 510500
Use Q_ASSERT instead of Q_CHECK_PTR for plain checks of pointer value2026-01-10T15:14:26ZFriedrich W. H. Kossebaukossebau@kde.org2026-01-09T15:16:48Zurn:sha1:5fff1e414a060c0619a97ad8d3f5665e3f5a4878
Q_CHECK_PTR (other than the name suggests) is intended only to check the
success of memory allocations.
Using it for any pointers instead can be misleading due to the
"Out of memory" log printed in case of hits.
Revert "Avoid implicitly selecting items"2025-11-12T14:54:30ZNate Grahamnate@kde.org2025-11-11T17:47:26Zurn:sha1:7419cd326902c64b69802ab3f01656076d3c7a97
This reverts commit 122fee5625f0285ec4ebda79162c72390989eb2a.
This behavior change was well-intentioned, but has significant usability
and speed drawbacks that have not been addressed:
- Keyboard-driven folder manipulation became slower
- Unexpected behavioral differences when opening files with the pointer
compared to when opening them with the keyboard introduced
inconsistency and cognitive load
- Unexpected opening of selection mode during fast operation introduced
the potential for confusion and additional errors
- Dolphin's behavior became inconsistent with that of other file
managers users may be accustomed to
The bug tracker, discuss.kde.org, and Reddit are full of complaints
about this change. It's been a year now; I think it's clear that many
Dolphin users have not gotten used to and accepted it. I have to count
myself as one of them, I'm afraid. I've tried to get used to it for a
year, but I just have not been able to.
I don't believe the benefits of this change outweigh the drawbacks, so
let's revert it.
24d859cf19e90fa22ed687b36a68231625c1bd80 was explicitly mentioned as a
thing that should also be reverted in this case, but it's already been
done.
BUG: 494125
BUG: 511966
CCBUG: 424723
CCBUG: 492404
FIXED-IN: 25.12.0
dolphin: improve keyboard search behavior for repeated characters2025-11-10T08:38:31Zweinan liliweinan@kylinos.cn2025-11-10T08:38:31Zurn:sha1:3858afbfa4f2f60cc33f39a471d36a1e1a3514c7
The original keyboard search implementation had a limitation when dealing with files containing repeated characters like 44.txt. When typing 44, it would trigger rapid navigation to the next item starting with 4 instead of matching the full string 44.
This patch introduces a smarter search strategy:
1. First attempt full string matching for exact file names
2. If full match fails and user is typing repeating characters, fall back to rapid navigation using either:
- Last successful search string (for extended searches like 444 -> 4444)
- First character only (original rapid navigation behavior)
The changes include:
- Modified changeCurrentItem signal to include a found parameter for search result feedback
- Added m_lastSuccessfulSearch to track successful searches for better fallback behavior
- Used Qt::DirectConnection to ensure synchronous execution for immediate result feedback
This provides better user experience when searching for files with repeated characters while maintaining the rapid navigation feature for quick browsing.
BUG: 501851
dolphinmainwindotest: harden some tests2025-10-23T08:10:58ZMéven Carmeven@kde.org2025-10-19T18:32:34Zurn:sha1:bc5627eec73e5df94f27ed4176ef543a3cc75d58dolphinmainwindowtest: prevent kaboutdata warnings2025-10-23T08:10:58ZMéven Carmeven@kde.org2025-10-19T18:14:32Zurn:sha1:239f5822600588b68877924deb3c75688e41eabeFix a couple compiler warnings2025-10-21T10:52:25ZMéven Carmeven@kde.org2025-10-21T10:52:25Zurn:sha1:d7dc3253d5b475b63811c1a6ded907a99e68059b