On Wednesday, August 17, 2011 22:52:14 Marco Martin wrote:
i would say ship it (well, after is tested :p)
ok; i'll try and find the time to test it. shouldn't be too hard to do so.
how does this sound? and does seem feasible enough?
i think so; it keeps backwards compatibility with a path
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102357/#review5784
---
thanks for the patch and noticing this issue.
what would
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102357/#review5785
---
editors/editpage.cpp
On Thursday 18 August 2011, Aaron J. Seigo wrote:
On Wednesday, August 17, 2011 22:52:14 Marco Martin wrote:
i would say ship it (well, after is tested :p)
ok; i'll try and find the time to test it. shouldn't be too hard to do so.
how does this sound? and does seem feasible enough?
i
On Thu, Aug 18, 2011 at 2:09 AM, Marco Martin notm...@gmail.com wrote:
i tought i explained it: a QMapQString, QString will never work.
you need to change it to QMapQString, QVariant, as easy as that
That doesn't work either (I had tried it when it was made QVariantMap in the
engine). It
On Thu, Aug 18, 2011 at 5:13 PM, Viranch Mehta viranch.me...@gmail.comwrote:
Component.onCompleted: {
var profiles = dataSource.data[PowerDevil][Available profiles];
// do stuff with the map, eg iterate
}
Fixed. The above code (for getting the map and iterating) had to be put
On Wednesday, August 17, 2011 17:29:28 Martin Gräßlin wrote:
On Wednesday 17 August 2011 16:56:36 Sebastian Kügler wrote:
Is there a workaround for this, or do hardware or driver simply not allow
using GLES on this machine?
try the attached patch - it should disable the check for GLES.
Hi all,
just an idea I had today: do we really need the opacity menu in the Alt+F3 menu?
Reasons against the menu:
* menu in tasks applet does not provide the opacity (missing consistency)
* Opacity is not really useful as both foreground and background are modified
(hard to read)
and no blur
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102027/
---
(Updated Aug. 18, 2011, 6:09 p.m.)
Review request for Plasma.
Changes
Am Thu, 18 Aug 2011 19:20:08 +0200
schrieb Martin Gräßlin mgraess...@kde.org:
Hi all,
just an idea I had today: do we really need the opacity menu in the
Alt+F3 menu?
I think it's just a leftover from the time when kwin used to control
kcompmgr.
I'd say the entire menu just is a mess.
Most
A Quinta, 18 de Agosto de 2011 18:20:08 Martin Gräßlin você escreveu:
Hi all,
just an idea I had today: do we really need the opacity menu in the Alt+F3
menu?
kill it die die :)
Reasons against the menu:
* menu in tasks applet does not provide the opacity (missing consistency)
* Opacity
Personally I don't see a good reason for having the opacity menu at all
and I found it kind of techy (look what we can do: isn't that awesome?
Translucent Windows!). So convince me to not remove it :-)
Cheers
Martin
I use it daily for my Konversation window
-
br
Eric
I don't know why do you want to break every single thing. Even the
most little ones. Is converting user's experience into a nightmare
your passion?
--
Cheers,
David
___
Plasma-devel mailing list
Plasma-devel@kde.org
- Ursprüngliche Mitteilung -
I don't know why do you want to break every single thing. Even the most
little ones.
Would you like to elaborate how this breaks anything? Would you please explain
why you consider the menu (not the functionality) so important? Please note
that I asked
On Donnerstag 18 August 2011 19:20:08 Martin Gräßlin wrote:
Hi all,
just an idea I had today: do we really need the opacity menu in the Alt+F3
menu?
Don't know if you need it, I use it regularly. Wouldn't mind moving it into the
Advanced
sub-menu, though.
15 matches
Mail list logo
