[PATCH] Re: KMix
Frans Englich
frans.englich at telia.com
Sun Dec 7 20:06:52 GMT 2003
On Sunday 07 December 2003 19:49, Aaron J. Seigo wrote:
> On Saturday 06 December 2003 12:25, Frans Englich wrote:
> just saving on Quit is probably good enough... Restore should probably
> remain, so you can play with the volumes safely with a way to backtrack;
> and if there's a Restore and Save should also probably be there...
Yes, that's weights back a little to more advanced users. But otoh, it
introduces an inconsistency compared to other situations when something is
changed be it settings or a document - if it's altered the user can choose to
manually save(by the save action) otherwise the use will be prompted when
he/she tries to exit. With this proposed behavior the user would perhaps be
confused when he/she sees the menu entries - "but I didn't ask it to save
the last time!"(and then the experience and thus usability is damamaged - a
feeling of distrust and that the program doesn't do what the user wants -
what do I need to do in order for making it behave in a way I can predict?).
We could prompt the user though, but it would introduce a string change and
the patch would be alot more intrusive. That's a no no.
I want to nuke the menu entries. From my experience as sound engineer you
don't use regulators in that way. And in those cases, it often involes
arithmethics which is possible because the knops/levers/displays are
dB-graded, which Kmix is not. KMix is a simple app for simple use, (lets keep
it that beautiful) - 99% of the users will regulate according to their ears,
a method which is amazingly underrepresented among sound engineers.
cheers,
Frans
More information about the kde-core-devel
mailing list