Version: (using Devel) Installed from: Compiled sources Using the little cashew on the right of the panel to adjust the height is very difficult and counter-intuitive. I used the cashew about 4-5 times to change my panel width, but for the life of me could not understand how to change the height of the panel. I attempted to click on the panel itself whilst the configuration rows were up, and "drag" it higher/lower. However, this did not work (and dropped me out of configuration! Oops!). I tried this for a few times, then gave up. I asked other users how to go about doing this, and only after I was instructed did I find the way. Would it be possible to: a) Have some sort of message/tooltip displayed when in configuration mode? (e.g. "To adjust the height of the panel please click and drag here ^^") b) Allow the user to drag the actual panel itself (when they click on the main boundary, not bounded by the screen) - kind of like kicker used to allow?
Another thought which occured to me: c) Would it be possible to have a "ruler" going both horizontal + vertical on the configuration panel, with a clear indication of where to click to change the height/width? Would be kind of cool! (and you could get an exact height of your panel!)
I really like that ruler idea. Another addition could be a small spinbox near the alignment buttons so you can manually enter the desired height/width immediately.
I Agree with Lucas: it should be possible to select manually the panel size.
Lucas: That was what I envisaged. You just put it into words a whole lot clearer than I could! So I agree with both of you!
After thinking about the ruler idea again I have just realised that they are not actually needed at all if the spinboxes exist as the spinboxes themselves are the "ruler".
@Lucas: you're right.
Related report: https://bugs.kde.org/show_bug.cgi?id=163875
*** Bug 163987 has been marked as a duplicate of this bug. ***
Related report: https://bugs.kde.org/show_bug.cgi?id=165196
buttons have been added with explicit labels on them.
*** Bug 165196 has been marked as a duplicate of this bug. ***