Adil wrote:
> --- Vincas Ciziunas <vi...@ci...> wrote:
>
>> Thought y'all would like to know that gaim seems to be reacting as
>> though fluxbox has some sort of a system tray. I even removed my
>> .gaim directory just to make sure that I didn't have some old gnome
>> configurations lingering about. When I close the buddy-list window,
>> other windows remain open and I have no way to get the buddy list
>> back. If I close all the windows, gaim keeps running.
>>
>
> I think I have seen this happen a few times at my end too when I start
> gaim from some temporary location (eg. gaim -c /tmp). I think what happens
> is this: the docklet keeps trying to add itself as a visibility manager,
> even after it fails to create itself (the call to docklet_x11_create_cb in
> docklet_x11_destroyed_cb is probably to blame). But I am not familiar with
> the code in the docklet, and I don't use it either (and other things keep
> eating my free time). So I haven't managed to dig any deeper.
>
I am working on fixing this, as it is somewhat related to another bug.
The destroyed_cb calling the create_cb is actually intended (imagine the
gnome panel crashes and restarts itself, the docklet window gets
destroyed and needs to get recreated). In this particular case, we need
to distinguish between gaim startup creation of the docklet and the
recreation of the docklet.
Related to this (the bug that I'm working on) is the timeout we use to
assume the docklet is a visibility manager, even before we receive
notification back that the docklet was embedded in the notification
area. I will change this timeout to only effect the initial creation,
not the recreation. In addition, the timeout will change from 5 seconds
to 10-30 seconds (haven't decided yet) if the docklet successfully
embedded the last time gaim was launched.
I've thought through this while driving, but haven't looked over the
code yet to make sure I'm approaching this right, so details may change. :-)
-casey
|
