On Thu, 2011-12-08 at 06:22 +0100, Nick Copeland wrote:
> > > > It's more like the distance along the minor axis controls
> sensitivity,
> > > > and the actual value change is always along the major axis?
> > >
> > > yes. also rather easy to discover.
>
> Does this differ from fanning sliders?
>
On 12/07/2011 09:03 PM, David Robillard wrote:
It's more like the distance along the minor axis controls sensitivity,
and the actual value change is always along the major axis?
Oh, I thought that's what happens with fan-sliders already ... and I
should know ;)
The 3D application Houdini ha
> > > It's more like the distance along the minor axis controls sensitivity,
> > > and the actual value change is always along the major axis?
> >
> > yes. also rather easy to discover.
Does this differ from fanning sliders?
_
On Wed, 2011-12-07 at 17:32 -0500, Paul Davis wrote:
> On Wed, Dec 7, 2011 at 3:03 PM, David Robillard wrote:
>
> > Hm... so my description wasn't quite what you'd want.
> >
> > It's more like the distance along the minor axis controls sensitivity,
> > and the actual value change is always along
On Wed, Dec 7, 2011 at 3:03 PM, David Robillard wrote:
> Hm... so my description wasn't quite what you'd want.
>
> It's more like the distance along the minor axis controls sensitivity,
> and the actual value change is always along the major axis?
yes. also rather easy to discover.
_
On Wed, 2011-12-07 at 14:43 -0500, Paul Davis wrote:
> On Wed, Dec 7, 2011 at 2:39 PM, Neil C Smith wrote:
> > How easy is that to use in practice though? With a mouse, and
> > particularly with a touch screen, it's not that easy to do a purely
> > vertical movement without introducing lots of ho
On Wed, Dec 7, 2011 at 2:39 PM, Neil C Smith wrote:
> How easy is that to use in practice though? With a mouse, and
> particularly with a touch screen, it's not that easy to do a purely
> vertical movement without introducing lots of horizontal "noise" that
> will surely hamper your attempts at f
How easy is that to use in practice though? With a mouse, and
particularly with a touch screen, it's not that easy to do a purely
vertical movement without introducing lots of horizontal "noise" that
will surely hamper your attempts at fine settings?!
Neil
On 7 December 2011 19:32, Paul Davis w
On Wed, Dec 7, 2011 at 2:12 PM, David Robillard wrote:
> How about using the axis inline with the slider for coarse control, and
> the other axis for fine control? For example, a horizontal fader would
> use horizontal drag as a "direct grab" as usual, but the vertical
> distance would be used a
On Fri, 2011-11-25 at 05:06 +0100, hermann wrote:
[...]
> But, as a first step, we could possible find a agreement about witch
> controller key will introduce the "fine settings mode", as far I see we
> have "control" or "shift". I will be cool if we could get a agreement
> witch one is to use.
Ra
On Fri, Nov 25, 2011 at 09:50:53PM +1300, Jeff McClintock wrote:
> Imagine your device supplemented with a 'dumb' pair of MIDI controllers
> complementing the two GUI sliders, they could not correctly implement the
> complex interaction between the two gain settings, therefore you need to go
> ba
On Thu, Nov 24, 2011 at 06:52:24PM -0500, David Robillard wrote:
> ... I guess you are being pedantic and jumping on me
> saying it's a "model" issue.
Dave, I I have no desire to 'jump on you', and replied to
something written by Nick if I'm not mistaken.
> Some situations are indeed much more
On Fri, Nov 25, 2011 at 09:52:25AM +0100, Nick Copeland wrote:
> All we are really talking about here is what actions give what inputs. Seeing
> as we
> all agree that placing semantics on the controls is way out of scope then
> specific
> exceptions may just have to be moved outside.
Agreed,
> From: d...@drobilla.net
> To: f...@linuxaudio.org
> Some situations are indeed much more complex than others, but a widget
> is still just a stupid thing that gives you a number.I go with this, for lots
> of reasons but the main one being that the graphic should be
an output of your application
plementing the two GUI sliders, they could not correctly implement the
complex interaction between the two gain settings, therefore you need to go
back and move that 'intelligence' into the model.
Best Regards,
Jeff
> Message: 18
> Date: Thu, 24 Nov 2011 20:45:09 +0000
> From: F
> > Is it possible to configure Macbook touchpads to middle click?
> >
> > -dr
> >
> > P.S. Spare us the "who cares" rants, please...
You can do this kind of stuff with the Mac. My boss has one and I had to use it
to do a presentation a while back: one button. Bummer. I had him drive the thing
Am Donnerstag, den 24.11.2011, 18:57 -0500 schrieb David Robillard:
> On Thu, 2011-11-24 at 21:31 +0100, hermann wrote:
> > Am Donnerstag, den 24.11.2011, 14:21 -0500 schrieb David Robillard:
> > > Middle click to "go here" is a convention from scroll bars dating back
> > > to the dawn of X11. Usi
On Thu, 2011-11-24 at 22:30 +0100, Nick Copeland wrote:
> > Just a thought, but perhaps an effort at a LAD HIG (Human Interface
> > Guidelines) might be a good idea, so things like this aren't
> arbitrarily
> > different between apps and plugins?
> >
> > Naturally the scope of such a thing would b
On Thu, 2011-11-24 at 21:31 +0100, hermann wrote:
> Am Donnerstag, den 24.11.2011, 14:21 -0500 schrieb David Robillard:
> > Middle click to "go here" is a convention from scroll bars dating back
> > to the dawn of X11. Using something easily done accidentally (and
> > unknowingly) for learn doesn'
On Thu, 2011-11-24 at 20:45 +, Fons Adriaensen wrote:
> On Thu, Nov 24, 2011 at 02:21:25PM -0500, David Robillard wrote:
>
> > Agreed. Everything here is about the *view*. How that maps to actual
> > parameter values is an underlying model issue.
>
> Not always. Consider the case of 'VCA'
On Thu, Nov 24, 2011 at 03:12:12PM -0800, Jeff Koftinoff wrote:
>
> On 2011-11-24, at 12:45 PM, Fons Adriaensen wrote:
>
> > Not always. Consider the case of 'VCA' groups for faders. That
> > is: you have a slider that controls the gain of a group of
> > channels (without those being mixed). The
On Thu, Nov 24, 2011 at 03:12:12PM -0800, Jeff Koftinoff wrote:
>
> On 2011-11-24, at 12:45 PM, Fons Adriaensen wrote:
>
> > Not always. Consider the case of 'VCA' groups for faders. That
> > is: you have a slider that controls the gain of a group of
> > channels (without those being mixed). The
On 2011-11-24, at 12:45 PM, Fons Adriaensen wrote:
> On Thu, Nov 24, 2011 at 02:21:25PM -0500, David Robillard wrote:
>
>> Agreed. Everything here is about the *view*. How that maps to actual
>> parameter values is an underlying model issue.
>
> Not always. Consider the case of 'VCA' groups f
Excerpts from hermann's message of 2011-11-24 21:31:22 +0100:
> Am Donnerstag, den 24.11.2011, 14:21 -0500 schrieb David Robillard:
> > Middle click to "go here" is a convention from scroll bars dating back
> > to the dawn of X11. Using something easily done accidentally (and
> > unknowingly) for
> Just a thought, but perhaps an effort at a LAD HIG (Human Interface
> Guidelines) might be a good idea, so things like this aren't arbitrarily
> different between apps and plugins?
>
> Naturally the scope of such a thing would be limited since different
> programs have different needs, but at l
On Thu, Nov 24, 2011 at 10:03:47PM +0100, Nick Copeland wrote:
> Wow. Isn't this a far bigger topic?
Agreed, yes. But I was replying to your suggestion that
the translation of 'widget value' to 'actual parameter
value' would always be the task of the model or DSP code.
That is in general not the
> From: f...@linuxaudio.org
> To: linux-audio-dev@lists.linuxaudio.org
> Subject: Re: [LAD] sliders/fans
>
> On Thu, Nov 24, 2011 at 02:21:25PM -0500, David Robillard wrote:
> Suppose the minimum value of the widget would correspond to say
> -100 dB if not handled speciall
On Thu, Nov 24, 2011 at 09:31:22PM +0100, hermann wrote:
> A click to "go here", seems on the other hand like a bad Idea for me.
It's almost always a bad idea - there is no corresponding action
using a 'real' control.
But there are some alternative uses. I've been using R-click for
* On an EQ:
> From: brumm...@web.de
> To: d...@drobilla.net
> CC: nickycopel...@hotmail.com; linux-audio-dev@lists.linuxaudio.org
> I think most modern apps use middle mouse button today for midi
> connection. Laptops witch didn't have a middle mouse button often even
> didn't have a midi in connection so the
On Thu, Nov 24, 2011 at 02:21:25PM -0500, David Robillard wrote:
> Agreed. Everything here is about the *view*. How that maps to actual
> parameter values is an underlying model issue.
Not always. Consider the case of 'VCA' groups for faders. That
is: you have a slider that controls the gain o
Am Donnerstag, den 24.11.2011, 14:21 -0500 schrieb David Robillard:
> Middle click to "go here" is a convention from scroll bars dating back
> to the dawn of X11. Using something easily done accidentally (and
> unknowingly) for learn doesn't seem like the best idea to me.
>
> That said, some lapt
> From: d...@drobilla.net
> To: nickycopel...@hotmail.com
> That said, some laptops don't have middle buttons...
Pretty sure they can all emulate with dual button click.
> > >
> > > This would have to be defined in relation to the underlying unit the
> > > controller is for, to address the quan
On Thu, 2011-11-24 at 20:02 +0100, Nick Copeland wrote:
> > From: d...@drobilla.net
> > To: nickycopel...@hotmail.com
> > > That is a good idea. The recent comments on the use of Shift vs
> > > Control
> > > and controller changes does highlight some differences. Bristol uses
> > > Shift for accele
> From: d...@drobilla.net
> To: nickycopel...@hotmail.com
> > That is a good idea. The recent comments on the use of Shift vs
> > Control
> > and controller changes does highlight some differences. Bristol uses
> > Shift for accelerator (as in shift your butt) and Control as a
> > decelerator
> >
On Thu, 2011-11-24 at 19:37 +0100, Nick Copeland wrote:
> > From: d...@drobilla.net
> > Just a thought, but perhaps an effort at a LAD HIG (Human Interface
> > Guidelines) might be a good idea, so things like this aren't
> arbitrarily
> > different between apps and plugins?
> >
> > Naturally the s
> From: d...@drobilla.net
> Just a thought, but perhaps an effort at a LAD HIG (Human Interface
> Guidelines) might be a good idea, so things like this aren't arbitrarily
> different between apps and plugins?
>
> Naturally the scope of such a thing would be limited since different
> programs have
On Tue, 2011-11-22 at 15:41 +0100, hermann wrote:
> Am Dienstag, den 22.11.2011, 09:25 -0500 schrieb Paul Davis:
> > On Tue, Nov 22, 2011 at 7:05 AM, James Morris wrote:
> > > On Tue, 22 Nov 2011 15:33:16 +0400
> > > Alexandre Prokoudine wrote:
> > >>
> > >> For darktable we examined the slider f
On Tue, Nov 22, 2011 at 4:05 PM, James Morris wrote:
> That looks interesting. I take it you removed the fan drawing code?
Hard to remove something that was never used :) We did it from scratch.
> What about imprecise but fine grained adjustments?
Ctrl is used for smaller steps right now.
Alex
Am Dienstag, den 22.11.2011, 09:25 -0500 schrieb Paul Davis:
> On Tue, Nov 22, 2011 at 7:05 AM, James Morris wrote:
> > On Tue, 22 Nov 2011 15:33:16 +0400
> > Alexandre Prokoudine wrote:
> >>
> >> For darktable we examined the slider from phat and created a similar
> >> new, more usable widget wh
On Tue, Nov 22, 2011 at 7:05 AM, James Morris wrote:
> On Tue, 22 Nov 2011 15:33:16 +0400
> Alexandre Prokoudine wrote:
>>
>> For darktable we examined the slider from phat and created a similar
>> new, more usable widget which combines a label and a slider. You can
>> enter precise value after a
On Tue, 22 Nov 2011 15:33:16 +0400
Alexandre Prokoudine wrote:
>
> For darktable we examined the slider from phat and created a similar
> new, more usable widget which combines a label and a slider. You can
> enter precise value after a right click inside the slider area, and
> you can use pretty
41 matches
Mail list logo
