| Summary: | Clicking the icon (of certain apps) in the systray brings up a default-size window | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Mikko C. <mikko.cal> |
| Component: | kdeui | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | 4plague, acheron, attilaolah, betonarbejder, cfeck, dkarnout, grundleborg, isit81, joris.guisson, kde, kwin-bugs-null, missive, null, ruchir.brahmbhatt, slsimic, teo, torotil, yionel |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Mikko C.
2008-02-06 22:06:27 UTC
Today this has been solved in Amarok 2: http://websvn.kde.org/?view=rev&sortby=date&revision=794074 So I'm guessing it's not a KDE bug like I thought. Hopefully Joris will fix it in KTorrent too ;) How can this solve anything ? The fix in amarok is just another way of saving and restoring the window size and position (which really should be done by calling KMainWindow::setAutoSaveSettings). The changes here do not even get called when the window is hidden or shown. I'm absolutely no programmer so I don't know. The only thing I know is that after *that* revision the bug is gone from Amarok :D Joris, can you reproduce the bug? If so, and if it's not a KTorrent bug, will you report it? Indeed this is very strange, I guess we can try doing the same as amarok, to see if it helps. *** Bug 161551 has been marked as a duplicate of this bug. *** OK, I have now done the same as amarok and the problem is gone. So there is certainly something going wrong with KMainWindow::setAutoSaveSettings uhm, for me, the problem is still present in rev803739. never mind, restarting KTorrent was not enough, I had to restart kde: now it seems to be working correctly :) Thanks *** Bug 181160 has been marked as a duplicate of this bug. *** The problem is still present in KTorrent-3.1.2 using KDE 4.2.00 in Ubuntu 8.10. Thanks a lot... I cal also confirm on kde 4.2.0 in opensuse 11.1. *** Bug 184499 has been marked as a duplicate of this bug. *** *** Bug 184719 has been marked as a duplicate of this bug. *** *** Bug 187313 has been marked as a duplicate of this bug. *** I cannot confirm in current trunk (r970844) for KTorrent. It remembers window size both from systray and between exits. Is there any remaining app which has this problem? Amarok (as of r971770) still has this problem, but only sometimes. That is, sometimes when I build it, the problem is there, but for other builds it is corrected. Right now, it's broken. *** Bug 209197 has been marked as a duplicate of this bug. *** It's back with Amarok 2.2 (NEON Ubuntu Jaunty repo). *** Bug 209505 has been marked as a duplicate of this bug. *** Amarok Neon now behaves properly even though I haven't upgraded it! (In reply to comment #20) > Amarok Neon now behaves properly even though I haven't upgraded it! No Amarok Neon have the bug :( The click on the systray button to show Amarok maximized not work. Amarok is nearly maximized but no maximized :(. So the bug is still here *** Bug 209806 has been marked as a duplicate of this bug. *** The bug is there for kTorrent 3.2.3 (kde 4.3.1) *** Bug 215092 has been marked as a duplicate of this bug. *** *** Bug 216497 has been marked as a duplicate of this bug. *** Let me understand this bug correctly. As I try on latest trunk, I see the following behavior (using KTorrent from trunk): Procedure I: Hiding a normal (unmaximized) window 1 Start a program A-> The size is the last used size 2 Hide it using systray 3 Show it using systray B-> The size is same as in A So far I see no error here. Procedure II: Hiding a maximized window 1 Start a program A-> The size is the last used size 2 Maximize it B-> The size is maximized 3 Hide it using systray 4 Show it using systray C-> The size is maximized, same as in B 5 Unmaximize/restore D-> The size is restored, but different than in result A. So what I see is only result D from procedure II is wrong. Correct? If any other result is different from what I see here, please state the exact bug. From what I understand, this is a kwin/NETWM bug. You cannot open a window maximized, and also tell it what the non-maximized size is. You could open non-maximized to tell it the correct size, then immediately maximizing it, but this would result in flicker. KWin maintainers: solution? To Christoph Feck: If this is the current problem, then it is far not that frustrating than it was when this bug was reported. IIRC the original problem was that when a window was moved to systray (i.e. a maximized window), and it was shown again, it was not the same size and position as before minimizing to systray. The remaining issue from comment #26 is bug 214325. Closing this one, assuming the original reported issue is fixed. |