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

List:       kde-bugs-dist
Subject:    [Bug 103215] kicker removes application link during application
From:       "Aaron J.Seigo" <aseigo () kde ! org>
Date:       2005-04-05 1:17:20
Message-ID: 20050405011720.15494.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=103215         




------- Additional Comments From aseigo kde org  2005-04-05 03:17 -------
Michael: interesting idea, but still a bit manual and would mean adding a lot of \
implied information to the painting of buttons. would have to consider how this would \
work with tiles. perhaps "grey" them out and make them innactive? copying .desktop \
files will create other complications, though, unfortunately.

Frerich: IMO best idea in this thread so far. thanks for offering some constructive \
problem solving =)

while driving to pick up Peyton from school it occurred to me that we can actually \
remove the button from the panel immediately but keep the actual container object \
around in memory and check a few times (say at 15s, 60s, 180s and 720s intervals?) to \
see if the referenced file/service returns. if it does then the button would reappear \
on the panel. if it doesn't reappear by the last check we assume that the file is \
gonzo and delete the object from memory for good.

perhaps taking a cue from Michael's idea the icon could become "innactive" and grey \
out for 5-10s before actually being removed, making quick remove/replaces not jostle \
things on the panel _too_ much. can't be too long, though, as it should be responsive \
for DnD actions. i'll have to experiment with that a bit.

this should give us the automatic behaviour, work with uninstall/reinstnall (assuming \
it completes within the span of that longest delay, which it should).

do you see any possible 'gotchya's with this approach?

at the extreme end an option could be added to kickerrc (and documented in the \
KConfigXT file, making is easy to discover and accessible via kconfigeditor) to \
completely disable all automatic watches so if you really want a manual system you \
can turn it off and leave a usable kicker for the Rest Of Us(tm).


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