>On Sunday 31 May 2009, dantti85-...@yahoo.com.br wrote:
>> What about doing the old test (isLocalFile || isRelativePath()), this would
>> keep the old behavior and add support for relative paths, i believe
>> something like http://path_to/thing.desktop will never be relative?
>
>hm.. probably not.
What about doing the old test (isLocalFile || isRelativePath()), this would
keep the old behavior and add support for relative paths, i believe
something like http://path_to/thing.desktop will never be relative?
Daniel.
- Mensagem original
De: Aaron J. Seigo
Para: plasma-devel@kde.or
The url for these relative paths are like
"Internet/kvirc.desktop", and how does
that http://foo/.../thing.desktop works? I mean
how can one input those?
We can test the url protocol but it actually depends more
on it being passed, like these relatives don't pass.
This patch is not completely actu
Hi,
there is a bug in kickoff when dealing with old applications
that install .desktop at applnk. KSycoca returns a relative
path and as David Faure said it should be handled in kickoff,
in the case what happens is that kvirc from kde3 when added
to favorites looses it's icon, and when added to the
>> PS: By the way, there is a bug about time configuration. By default, update
>> interval of digital-clock plasmoid is 60 seconds when showSeconds is false,
>> and 1 second if it's true. If you change time from clock kcm and
>> showSeconds is false, digital-clock applet refreshes itself 1 minute
>sorry, what does moving the mouse wheel over the battery icon have to do >with
>the brightness of my screen?
>
>at the very least it requires onscreen notification, but it really seems >like
>an odd feature.
I do agree, and imho it could be changed to do another thing, like changing
power prof
Yep,
i got this problem too,
i think some app is stealing this signal.
i solved this rmoving my .kde4 :P
But i definitely don't promote this kind of
"solving problems" :)
Daniel.
- Mensagem original
De: Michael Jansen <[EMAIL PROTECTED]>
Para: plasma-devel@kde.org
Enviadas: Quarta-fei
something is killing kded4,
you can avoid logout and login by just
starting kded4 again.
you can try to start kded4 on a shell
and open KRunner to see if you find something.
Daniel.
- Mensagem original
De: Guillaume Pothier <[EMAIL PROTECTED]>
Para: plasma-devel@kde.org
Enviadas: Segund
