[Bug 287228] onMeeGo: while the device is plugedIn, the battery symbol vanishes, so that options like sleep cannot be activated
Thomas Pfeiffer
colomar at autistici.org
Tue Nov 22 16:19:34 UTC 2011
https://bugs.kde.org/show_bug.cgi?id=287228
--- Comment #11 from Thomas Pfeiffer <colomar autistici org> 2011-11-22 16:19:33 ---
> I wonder if it's justified to add powerbutton chrome to the panel though.
> Right now we combine that with the battery display and cross fingers that the
> user either finds the battery (if it's there at all), or find the physical
> powerbutton, which I've wired to suspend (doesn't seem to work for everybody).
>
> The problem of course with hiding the battery when fully charged (which I
> think makes sense at least on a desktop, but feels a bit uncommon on a mobile
> device) is that we bastardize it to not be just informational, but also
> provide access to settings and suspend actions.
>
> On the desktop, the battery icon can still be shown even if hidden, but that
> option isn't available in PA's system tray (neither by settings UI, nor by
> this little arrow that makes it show).
+1, that's why I'd vote for a separate button (different icon than the big red
power button, of course ;)
> > > Well that's pretty much like the traditional shutdown plasmoid with PA
> > > look & feel, isn't it?
> > > (
> > > http://ubuntu.paslah.com/wp-content/uploads/2011/08/The-desktop-menu-Leav
> > > e.png )
>
> Similar, but the feel should really be different, the lock/logout dialog just
> doesn't feel very touch-friendly.
Yes, sure. These mockups look touch-friendly enough for me, though. Big buttons
with enough space between them, no combo buttons, nice.
> Hibernate requires swap, which mobile devices usually don't have.
Oh, I didn't know that. What does the hibernate button currently in the battery
icon menu do, then?
> Nice work, overall.
Agreed. Much better suited for a tablet than the menu dropping form the battery
icon
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Active
mailing list