[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 58901] kmix doesn't dock reliable
From:       Christian Esken <esken () kde ! org>
Date:       2007-04-28 9:55:06
Message-ID: 20070428095506.5149.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=58901         




------- Additional Comments From esken kde org  2007-04-28 11:55 -------
Josh, I can't tell whether this is still a problem or not. All I can say is that I \
haven't done anything to fix it (as described in comment 27 I don't know how to fix \
or reproduce it). The whole situation is very tricky. I'll summarize it here:
1) I have to workaround a possible exit-by-systray issue, otherwise the KMix window \
would ALWAYS be hidden on login (Systray-Quit would close/hide the window and I got a \
wrong state) 2) Then there is the fact that KMix is a KUniqueApplication. This causes \
a start of KMix to behave differently: On the first start, KMix is really started. On \
the secnd start, KMix is just shown. This behaviour conforms to user expectations, \
but can lead to undefined results - if KMix is started twice  (e.g. some global \
autostart and user session), KMix would always start shown (independent from the \
configured value). 3) Then there is KMilo. KMilo will start Kmix if it doesn't find \
it. This can lead to undefined results: 3a) If KMilo is run AFTER KMix is restored \
from the session, everything is fine (KMilo would find a running KMix, and thus will \
not start it again).  3b) If KMilo is run BEFORE KMix is restored from the session, \
the bug hits: KMilo will not find KMix, and start it. Then the session restoration \
will start KMix again AND thus (see point 2) KMix will be shown.

Final words:
A) The KMilo / KMix collaboration is suboptimal. It depends a lot on the startup \
timing whtether the problem will show up on your box or not. A possible (but \
untested) soulution is to backport the "--keepvisibility" command line parameter as \
implemented in KDE4's KMix, and to implement using it in KMilo. Due to time \
constraints I am not able to do this backport - volunteers for this task are welcome \
and should contact me (preferable directly by email). B) Some problems can't be \
avoided. If KMix is started twice (Session+Autostart or \
Global_Autostart+User_Autostart), you have lost and I don't see a solution for that \
right now.  
  Christian


[prev in list] [next in list] [prev in thread] [next in thread]