On Fri, May 15, 2009 at 09:25:00AM +0200, Eduardo Robles Elvira wrote:
> we can guess the future usage and get a good
> enough predictions for most of the time. You've been using 10W+-2W for
> last 10 mins, and in 10mins the battery has decreased 2%. We can
> predict that if the battery usage cont
as I might have mentioned either in this list and/or the irc
channel, I'm very fond of the panel spacer that's in playground right
now. I even hacked a little in the Plasma::Applet class so the default
policy is not to ocupy as much as possible, but to yield to greedy
applets (commit 915261),
On Sat, Dec 27, 2008 at 05:49:49PM -0700, Aaron J. Seigo wrote:
> > here are a couple of patches, one against kdelibs/plasma and the
> > other for playground/base. what's insteresting about the last one is
> > that as the policy is always the same, I tried to set it in the
> > constructor, but
On Thu, Jan 22, 2009 at 02:28:52AM +, Sebastian Kügler wrote:
> M +1 -1 CMakeLists.txt
> A lionmail (directory)
> A lionmail/CMakeLists.txt
> A lionmail/desktoptheme (directory)
> A lionmail/desktoptheme/akonadi.svg
> plasmob
On Thu, Jan 08, 2009 at 10:49:37PM +0100, Sebastian Kügler wrote:
> > will do after this patch is in and/or I return from vacations next
> > week :)
>
> Ok. Can you send me an updated patch I can commit directly then?
duh, forgot to attach it :|
--
(Not so) Random fortune:
13:21 < prope
On Thu, Jan 08, 2009 at 03:11:44PM +0100, Sebastian Kügler wrote:
> No. Percentage and charge state are two unrelated things. The battery is not
> full when a certain percentage is reached, but when Solid (HAL) says it's
> fully charged. For some, worn out batteries that could even be 30%. So don
On Wed, Jan 07, 2009 at 09:40:13PM +0100, Sebastian Kügler wrote:
> - 100% might not be correct, my battery often is fully charged at 98%,
> display
> the actual charge rate there
you mean, when the percentage is more than, say, 95%, show the
percentage anyways?
> - showLabel() in configAcc
On Tue, Jan 06, 2009 at 03:32:04AM +0100, Sebastian Kügler wrote:
> - the changes in updateStatus() seem a bit random, and I don't grok all of
> them, would be good if it was removed.
> - Making the label wider than 4 chars starts to randomly stretch it. We need
> a
> way to keep that label
On Tue, Jan 06, 2009 at 03:32:04AM +0100, Sebastian Kügler wrote:
> On Tuesday 06 January 2009 01:14:03 Marcos Dione wrote:
> > the third one is avoidable, really. I coded it so when the battery
> > is fully charged it shows 'Charged' instead of 0:00. the problem
as I mentioned in IRC, I have a patch for this. as sebas and aseigo
suggested, I'm sending it here.
now, right now there are 3 bugs: the remaining time, either for
total discharge when the AC is plugged off and the complete recharge
time when the AC is plugged back in.
the first one
On Fri, Dec 26, 2008 at 11:31:22PM -0700, Aaron J. Seigo wrote:
> On Friday 26 December 2008, Marcos Dione wrote:
> > hi all. I'm set to get the panel spacer to its previous behaviour
> > when set to auto stretch, that is, to use as much space as possible.
>
> this a
hi all. I'm set to get the panel spacer to its previous behaviour
when set to auto stretch, that is, to use as much space as possible.
now, the code is simple: it takes the size of the container (if it's
an horizontal panel, it takes the width), then loops through all the
applets/plasmoid
On Fri, Dec 26, 2008 at 01:06:32AM -0200, Marcos Dione wrote:
> On Mon, Dec 22, 2008 at 01:53:11PM +0100, Marco Martin wrote:
> > On Monday 22 December 2008, Aaron J. Seigo wrote:
> > > right now it starts an infinite loop when put into a panel, recalculating
> > &
On Mon, Dec 22, 2008 at 01:53:11PM +0100, Marco Martin wrote:
> On Monday 22 December 2008, Aaron J. Seigo wrote:
> > right now it starts an infinite loop when put into a panel, recalculating
> > it's size over and over.
>
> i changed the minimum needed to avoid the infinite resize loop.
hi m
I've been annoyed with this bug for some time now, so I wrote a
first (and second) patch. the second one puts the date and/or timezone
at the right od time. the only problem is that it doesn't calculate the
size it should take, so the time shows a little smaller that it should.
the problem is
15 matches
Mail list logo
