Bug 194992 - Toolbar buttons change locations
Summary: Toolbar buttons change locations
Status: RESOLVED DUPLICATE of bug 173764
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-02 15:31 UTC by mike_knichel
Modified: 2010-02-19 12:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Image 1 (38.61 KB, image/png)
2009-06-02 15:32 UTC, mike_knichel
Details
Image 2 (36.91 KB, image/png)
2009-06-02 15:33 UTC, mike_knichel
Details
Image 3 (35.36 KB, image/png)
2009-06-02 15:34 UTC, mike_knichel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description mike_knichel 2009-06-02 15:31:43 UTC
Version:           Kate 3.2.2 (using KDE 4.2.2)
OS:                Linux
Installed from:    Debian stable Packages

I use kate as my text editor. If I have many files open and wish to close them all or a bunch of them, as I start clicking on the close button, the locations of the buttons seems to change as I close files and I cannot cimply click multiple times on the close as it might be the "save as" button next....  I have screen shots to prove it if necessary but do not see how to add them to this bug report.

--
JuJuBee
Comment 1 mike_knichel 2009-06-02 15:32:43 UTC
Created attachment 34195 [details]
Image 1

Notice the location of the close button (and others) before closing a file.
Comment 2 mike_knichel 2009-06-02 15:33:25 UTC
Created attachment 34196 [details]
Image 2

Notice the location of the buttons after closing a file.
Comment 3 mike_knichel 2009-06-02 15:34:12 UTC
Created attachment 34197 [details]
Image 3

And again they change positions after closing a file...
Comment 4 Māris Nartišs 2010-02-14 17:19:23 UTC
It's a duplicate of an old and well known bug #173764 (yeah, this really sucks!)
Comment 5 Dominik Haumann 2010-02-19 12:25:06 UTC

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