Bug 206875

Summary: konsole - Dimensions (W x H) are not displayed on resize any longer
Product: [Applications] konsole Reporter: David Rankin <drankinatty>
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: adaptee, finex, zilla
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Unspecified   
Latest Commit: Version Fixed In:

Description David Rankin 2009-09-09 17:01:00 UTC
Version:            (using KDE 4.3.1)
Installed from:    SuSE RPMs

Dev's,

    I think this regression just happened. When resizing konsole, I used to get the terminal size ( char width x height) displayed when resizing konsole. The readout would be in a little box shown in the center of the konsole window as shown here:

http://www.3111skyline.com/download/openSUSE_bugs/kde4/screenshots/konsole-no-dimen-crp.jpeg

    Now the dimension is not displayed until after the resize is complete and then the dimension is splashed on the screen for at most 1 second. This is unexpected and did not begin until kde 4.3.1. I distinctly recall having used the readout in the past to set the konsole height and width to 110 x 50 for example. Now you can no longer do that because you don't seen the dimension until after you let go of the mouse. The readout should be visible during the resize operation so it is useful to the user.

    To get the screenshot showing the dimension, I had to resize the window, not release the mouse until I was ready to capture the screen, then simultaneously release the mouse and press print-screen. That was the only way to capture it. This should be fixed.
Comment 1 FiNeX 2009-09-09 22:59:53 UTC
Cannot reproduce using trunk :-)
Could it be a problem only in 4.3.1 ?
Comment 2 Kurt Hindenburg 2009-10-19 01:04:00 UTC
It works here, it is just not a popup window that is always visible..
Comment 3 Jonathan Wakely 2010-07-22 13:29:47 UTC
same issue as Bug 209758 ?
Comment 4 Jekyll Wu 2011-07-30 17:59:05 UTC

*** This bug has been marked as a duplicate of bug 209758 ***