Re: [linux-audio-dev] mouse wheel behavior and RFC: human interface guidelines

On Mon, 2004-08-23 at 11:19, Paul Winkler wrote: > On Sat, Aug 21, 2004 at 04:22:36PM -0400, Lee Revell wrote: > > I suspect that a GUI programmer or interface designer would expect > > things to increase from top to bottom. In GUI programming, the origin > > is at the top left of the screen, and

[linux-audio-dev] a new patent to worry about

http://news.harmony-central.com/Newp/2004/L3.html

[linux-audio-dev] Jackbeat : contributors needed

Hi, I feel like it's not a usual way to ask for contributions, but, well, I thought I'd give it a try : I'm the author of Jackbeat, at http://xung.org/jackbeat, and my day job's currently eating my time. I've just released the 0.3 development version which is a rewrite, forked from the (quite) stab

Re: [linux-audio-dev] Howto grab keys?

Paul Davis wrote: > if simply getting ascii characters from ncurses is enough, then this message doesn't matter. but if you start to want to use modifiers combined with keys (e.g. Alt-a, Ctrl-F1), you need to move beyond the normal ncurses model. if you take a look at the ardour ncurses front end

Re: [linux-audio-dev] mouse wheel behavior and RFC: human interface guidelines

On Sat, Aug 21, 2004 at 04:22:36PM -0400, Lee Revell wrote: > I suspect that a GUI programmer or interface designer would expect > things to increase from top to bottom. In GUI programming, the origin > is at the top left of the screen, and X,Y coorinates increase going > right and down respective

Re: [linux-audio-dev] Re: mouse wheel behavior and RFC: human interface guidelines

At Sun, 22 Aug 2004 15:18:52 +0200, Artem Baguinski wrote: > > people do not need consistent experience, people need to get the work > done. consistency is one of the tools that make getting the work done > easier, but it isn't a goal in itself. ++kudos; --Pete "Nothi