On Tuesday, November 30, 2010, Ivan Čukić wrote:
> There are a few things more that need to be done for 4.7:
> - In 'Adwanced Window/Application Settings' - show on specified/all
> activities - an application should be able to request to be on all
> activities (because it handles them internally -
For me, both approaches have drawbacks - either I need to set a group
of windows to be on one activity only, or to set them to be on all
activities.
There are a few things more that need to be done for 4.7:
- In 'Adwanced Window/Application Settings' - show on specified/all activities
- an applica
hi all ...
so recently application windows have started to be associated by default with
the activity they were started in.
after using it for a while now, i have found that it is becoming increasingly
annoying. and for the same reason that hard-wiring virtual desktops and
activities together
On Tuesday, November 30, 2010, Sebastian Kügler wrote:
> If you're trying to do this manually, you're opening a can of worms. The
> problem has also already been solved in KLocale.
indeed it has: KLocale::formatNumber(..), as in:
QString formatted = KGlobal::locale()->formatNumber(number, precisi
On Tuesday, November 30, 2010 20:39:07 Matthias Fuchs wrote:
> > no, keep it simple. kb is a good granularity. one unit keeps visual scan
> > comparisons easy. adding separators would probably help with that.
>
> Yes I like that myself as it is clean and simple. So I'll see if I come
> around upd
Am Dienstag 30 November 2010, 19:03:55 schrieb John Tapsell:
> On 30 November 2010 16:08, Matthias Fuchs wrote:
> > how it is displayed to the user:
> > 1) 56 K
> > 2) 3.7 M
> > 3) 5 G
>
> It takes a lot more effort to see that the last item is using more
> memory. Especially if you're not that
Am Dienstag 30 November 2010, 19:21:18 schrieb Aaron J. Seigo:
> On Tuesday, November 30, 2010, Matthias Fuchs wrote:
> > Actually the first suggestion would use KLocale::formatByteSize , while
> > the second one would keep the current state, yet still makeing the
> > numbers more readable imho.
>
On Tuesday, November 30, 2010, Matthias Fuchs wrote:
> Actually the first suggestion would use KLocale::formatByteSize , while the
> second one would keep the current state, yet still makeing the numbers more
> readable imho.
using a separator (giving "600,000") is probably a reasonable idea, but
On 30 November 2010 16:08, Matthias Fuchs wrote:
> how it is displayed to the user:
> 1) 56 K
> 2) 3.7 M
> 3) 5 G
It takes a lot more effort to see that the last item is using more
memory. Especially if you're not that comfortable with the K, B, G
meanings.
The "56 K" takes up more room and lo
Am Dienstag 30 November 2010, 18:05:04 schrieb Sebastian Kügler:
> On Tuesday, November 30, 2010 17:08:52 Matthias Fuchs wrote:
> > Am Montag 29 November 2010, 23:02:50 schrieb Sebastian Kügler:
> > > On Monday, November 29, 2010 22:25:29 Matthias Fuchs wrote:
> > > > What do you think on the idea
On Tuesday, November 30, 2010 17:08:52 Matthias Fuchs wrote:
> Am Montag 29 November 2010, 23:02:50 schrieb Sebastian Kügler:
> > On Monday, November 29, 2010 22:25:29 Matthias Fuchs wrote:
> > > What do you think on the idea I mentioned above, i.e. not using one
> > > "size" (KB, MB), but those th
Am Montag 29 November 2010, 23:02:50 schrieb Sebastian Kügler:
> On Monday, November 29, 2010 22:25:29 Matthias Fuchs wrote:
> > What do you think on the idea I mentioned above, i.e. not using one
> > "size" (KB, MB), but those that fit best, like in Dolphin? Actually only
> > if it is possible fro
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6005/#review9051
---
Ship it!
Have you tried removing the space again after you've cha
> On 2010-11-30 01:04:03, Davide Bettio wrote:
> > Should we apply this patch while waiting someone who fix this bug in Qt?
>
> Aaron Seigo wrote:
> sure (if only because the bug has been closed as "out of scope"), but
> annotate the code with a comment explaining the situation and a link t
> On 2010-11-30 01:04:03, Davide Bettio wrote:
> > Should we apply this patch while waiting someone who fix this bug in Qt?
>
> Aaron Seigo wrote:
> sure (if only because the bug has been closed as "out of scope"), but
> annotate the code with a comment explaining the situation and a link t
> to be clear: are you wanting the UI to show all matching items in a list
> beneath the line edit, or are you wanting it to just complete the "best"
> match
> in-line?
>
I'd like to complete the best match in-line, either as an autocompletion in
the LineEdit itself (like in the KRunner text field
> On 2010-11-30 01:04:03, Davide Bettio wrote:
> > Should we apply this patch while waiting someone who fix this bug in Qt?
>
> Aaron Seigo wrote:
> sure (if only because the bug has been closed as "out of scope"), but
> annotate the code with a comment explaining the situation and a link t
17 matches
Mail list logo
