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

List:       kde-panel-devel
Subject:    [Bug 160156] I'd like an option to always use two rows on the taskbar
From:       "Aaron J.Seigo" <aseigo () kde ! org>
Date:       2008-03-31 17:18:46
Message-ID: 20080331171846.20024.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=160156         




------- Additional Comments From aseigo kde org  2008-03-31 19:18 -------
Rafal: as i said already, the solution to positional movement (spacial memory \
invalidation) is to always move left-right, top-to-bottom in placement.

 Emil: the point is that configuration options are not a substitute for fixing \
problems.

consider: what is the better solution to "My elbow hurts when I move my arm": \
"Instead of using your arm, move things with your feet." or "Get a doctor to look at \
your elbow if the pain persists and if necessary get treatment for the elbow."

configuration options are fine when they actually provide a meaningful bit of value. \
when they are simply used as a way to more easily work around a problem, they are not \
just not useful they are *hazardous* to the code base.

when you add an option, it's really hard to ever take it back again (i've blogged \
about this some three years ago!) and every option complicates the code base. so if \
you are just working around problems that would have *real* fixes, then it's really \
shortsighted to put such a work around in place.

and what i'm saying is that this option would be exactly such a work around.
_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


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