[frameworks-kconfig] [Bug 430521] Dolphin doesn't restore to original size after resuming from maximized.

[Antonio Orefice]

https://bugs.kde.org/show_bug.cgi?id=430521

Antonio Orefice <kokoko3k at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|WAITINGFORINFO              |---
             Status|NEEDSINFO                   |REOPENED

--- Comment #25 from Antonio Orefice <kokoko3k at gmail.com> ---
(In reply to Nate Graham from comment #24)
> For anyone still experiencing the bug, can you try moving aside your
> ~/.config/dolphinrc file and trying again? This will check to see if stale
> config file entries could be causing the bug.

Yep, starting from a newly generated file, it works as intended, as stated
here:
https://bugs.kde.org/show_bug.cgi?id=434825

However, the "intended" way raised some concerns about the  removal of the
search bar, quoting myself:

>  Also, the decision to move the url navigation widget 
> to the toolbar raises problems for the ones that 
> like to have text in the toolbar itself, because
> enabling it breaks url navigation widget
> alignment with the file view area.
> moving the url navigation thing outside 
> of the toolbar raises the described problem again.

> Another thing i noticed when i deleted dolphinui.rc,
> is that the -previously present- "search toolbar", went gone.
> It could be handy because one can use it to
> accomodate url navigation bar, sacrifying some 
> space for the places panel.

https://bugs.kde.org/show_bug.cgi?id=434825#c10
https://bugs.kde.org/show_bug.cgi?id=434825#c11

...so basically the ones left with an old working configuration file have to
choose to have resize problems (keep old file) or possibly disalignment of
widgets when their sizes don't fit the intended position (...)

I think the right way of handling this change would be the ability to keep the
search bar and have dolphin able to properly resize itself, not asking users to
delete their -previously working- configs.

I understand the needs to simplify things, but not when that breaks working
environments.
This is happening more and more lately (Sorry.).

-- 
You are receiving this mail because:
You are on the CC list for the bug.