Add Dolphin view opacity slider and fix transparency issues#270
Merged
Bali10050 merged 7 commits intoBali10050:featurefrom Jan 17, 2026
Merged
Add Dolphin view opacity slider and fix transparency issues#270Bali10050 merged 7 commits intoBali10050:featurefrom
Bali10050 merged 7 commits intoBali10050:featurefrom
Conversation
- Implement 'DolphinViewOpacity' slider to allow granular control over Dolphin's main view transparency. - Deprecate the 'TransparentDolphinView' boolean, including a migration path for existing user configs. - Fix a bug where Dolphin transparency was lost in folders without scrollbars by ensuring rendering logic runs for empty scroll areas. - Restructure the Transparency configuration tab with a 3-column QGridLayout for perfect alignment of all elements. - Add QEvent::Resize triggers to ensure the blur region remains accurate when windows are maximized. - Include unit tests in 'kstyle/tests/' to verify the new opacity configuration logic.
- remove a redundant code block in darklystyleconfig.cpp for aligning widgets - optimized the Dolphin view search. Now only scans 'QAbstractScrollArea' children
- Fix crash by applying migration in-memory only; save on user confirmation - Change migration target to 0% (fully transparent) to match legacy boolean. - Force config re-read on load to correctly handle manual file edits.
Author
|
@Bali10050 Let me know what you think. tested on Plasma 6.5.5 |
Owner
|
It mostly looks good to me, I think there should be a separate control to remove that rounded view area, but that can be easily added later. Thank you! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I worked on this in an attempt to address this problem: #269
Problem Summary:
The main issue, is that in order to achieve translucency with title bars and the dolphin view area, you need to edit your colortheme file. This is obviously not ideal for less experienced users and comes with a number of issues.
While attempting to make dolphin translucent through my colortheme file, I noticed the alpha value applied to the view background was also affecting my System Settings, or small panels within it, and also the Wallpaper Manager. In the case of the Wallpaper Manager this resulted in full transparency without a blurred background.
MAJOR CHANGE: The checkbox to set dolphin to be transparent has been replaced with a slider on the transparency tab. The checkbox has been removed. Users can now control the opacity level directly from within the Darkly settings.
Why:
This feature adds an opacity slider for the "View" aspect of the Dolphin file manager, allowing the user to add transparency to Dolphin from Darkly, without having to manually editing a colortheme file.
How:
tooltips.
DolphinViewOpacity = 0-100 (int)Compatibility:
Migration logic converts the old boolean setting. If TransparentDolphinView=true is detected, the new slider defaults to 0% (fully transparent). This runs in-memory to avoid modifying user configs until they explicitly save settings.
Testing:
Unit tests are included in the PR and were ran to verify that settings are preserved.