From: Andre P. <oz...@al...> - 2003-01-13 07:10:23
|
On Mon, Jan 13, 2003 at 03:31:02AM +0000, Heimo Claasen wrote: > I beg to differ - I didn't recommend any change for Sweep's key > settings in general and for anyone else but wondered about the > possibilities to change these for one's own preferences (via > some script or config file). Sorry, what I meant was that we should not allow users to pick their own key settings, and force them to use one single keyboard layout. This is the exact opposite of what you're suggesting above :). I'd recommend this for the simple reason of consistency: moving from one PC with Sweep to another PC with Sweep guarantees the same accelerator keys on both PCs. I can't think of a single Windows or Macintosh sound editing program which allows you to customise its key bindings, and I don't feel like those programs limit my editing capabilities because the accelerator keys have been chosen with care; there's nothing I want which makes me think "I wish this key was different" or "I wish this feature had a key for it". In other words, if some menu options or features would greatly benefit from accelerator keys, let's talk about them here so that Conrad can define an accelerator key for it which then benefits _all_ users, not just a single person. Chances are, if _you_ want a particular key, somebody else out there wants it -- and they don't _know_ they want it. When they see a new release of Sweep with such a key binding, they may think "Hey, this is cool! I didn't even know I wanted this!". That's the philosophy behind my suggestion -- benefit all users and keep a consistent, standardised keyboard layout. > More important, there _is_ no "standard". At most, what Conrad > decides to use is creating a setup for Sweep (and for nothing > else). With some of the key uses, he said once, he took some > inspiration form a seemingly well distributed Windows editor > (which I don't know). But basically it's depending on his > insight, intuition, and preferences - others might have others. I understand your point, but those others (including users) can be wrong. The gtk+2 toolkit took out the capability to change accelerator keys in the menu precisely for this reason: they saw the value of consistency and decided it was better to be consistent and standardised than to be completely customisable. -- #ozone/algorithm <oz...@al...> - trust.in.love.to.save |