[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: QString questions for menubar usability
From:       Remi Villatel <maxilys () tele2 ! fr>
Date:       2006-09-13 18:17:47
Message-ID: 200609132017.47657.maxilys () tele2 ! fr
[Download RAW message or body]

On Wednesday 13 September 2006 07:12, Aaron J. Seigo wrote:

> indeed. these days style writers are fairly often doing very dubious
> things to widgets that sometimes have nasty side effects. i wish they
> wouldn't.

I read your blog but since Serenity doesn't do any of the mentioned bad 
things (I already fixed the only one), I had to find another one.  ;-)

> > Are you sure there isn't another way to achieve the same effect?
>
> yes, one might suggest setting PM_MenuBarItemSpacing to the value of the
> widgth of a _ in the font being used.

Well, no. The purpose of my hack is to remove the space in between the items 
so that the mouse never "falls into a void". As I wrote, I set 
PM_MenuBarItemSpacing to 0 before to enlarge the items.

> as for the qstring usage, using prepend and append is usually faster. i
> remember benchmarking this a year or two ago...

I will rather use char instead of char* as Frans Englich suggests. To 
me, "prepend" and "append" are a bit exaggerated for just one char.

Any way, even if the method isn't good, I think the idea is a step in the 
right direction according to Fitts' law "Bigger target, easier target". For 
the time being, I'll keep my hack with a switch to disable it by default... 
until somebody finds a "legal" way to do the same thing.

-- 
==================
Remi Villatel
maxilys_@_tele2.fr
==================
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]