On Wednesday 28 August 2013 21:19:15 Aaron J. Seigo wrote:
i think this is a question that we will only really get to a proper answer
once we work on consistent typography in a meaningful fashion. that will
tell us exactly what we need.
so for now my suggestion would be to flag this
On Tuesday 27 August 2013, you wrote:
On Wednesday 14 August 2013, Aaron J. Seigo wrote:
On Tuesday, August 13, 2013 13:33:36 Sebastian Kügler wrote:
On Tuesday, August 13, 2013 12:03:31 Marco Martin wrote:
mSize is fine, or also the recent addition
mSize is going to be a problem
On Wednesday 14 August 2013, Aaron J. Seigo wrote:
On Tuesday, August 13, 2013 13:33:36 Sebastian Kügler wrote:
On Tuesday, August 13, 2013 12:03:31 Marco Martin wrote:
mSize is fine, or also the recent addition
mSize is going to be a problem in the future, as it's gone from the API
hm. I already started porting things to unit.gridUnit...
I am happy to use whatever you guys suggest.
You just need to agree on one thing :)
I will wait until then.
Cheers
Mike
___
Active mailing list
Active@kde.org
On Wednesday, August 14, 2013 17:54:59 Marco Martin wrote:
btw, so the suggested way remains mSize?
for now i think it’s the least worst thing we have.
in future we ought to do something smarter ...
both units and font tie the value to something on screen: either screen
resolution (which iirc
Hi,
my mentor and I would like to get a second opinion from a plasma developer
regarding pixel based margins in plasma active applications. The question
emerged from https://git.reviewboard.kde.org/r/112013/ but is obviously a
general problem that needs to be solved the same way throughout the
