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

--- Comment #3 from tuxtor...@openmailbox.org ---
I did some testing, and it looks like it comes from the toolviews, specifically
from the bottom one.

I attached a commented testing session with the different actions I made.

The Bottom Toolbar has a constraint on its size driven by the size of the names
of the tools it is showing. Plus an extra empty space on the right.
Where the left and right toolbars can overflow, the bottom one can't, so it
resizes the whole window and forces it to follow its constraints.
Furthermore, when changing modes (main/debug/execute/…), the Toolbox statuses
aren't saved completely (saved when «right click>Tool View Position>…» but not
when «right click>Remove Tool View» and «right click>…(add tool view)»), and
when changing modes back, some tools change to other toolboxes, making them
grow suddenly.

So the ideal case would be to always remember where the tools where, and to be
able to overflow the bottom toolbox too, or even better, wrap the tools, in all
of the toolboxes.



In the code, I came across this code block:

    kdevelop/kdevplatform/sublime/idealbuttonbarwidget.cpp: 164-170

    //apol: here we set the usual width of a button for the vertical toolbars
as the minimumWidth
    //this is done because otherwise when we remove all the buttons and re-add
new ones we get all
    //the screen flickering. This is solved by not defaulting to a smaller
width when it's empty
    int w = button->sizeHint().width();
    if (orientation() == Qt::Vertical && w > minimumWidth()) {
        setMinimumWidth(w);
    }

Even though it is talking about the vertical bars, it's the minimumWidth that
is set.

There might be a link between this code and the strange behaviour.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to