From: Jonathan Woithe <jwoithe@ph...> - 2008-04-16 23:13:50
> > > When I pull down the output channel combo box, as I move the mouse along
> > > the different outputs, the output is changing. I would expect the change
> > > not to occur until I click the new output.
> > This is a consequence of Qt/PyQt and how it works - the combobox widget
> > broadcasts "value changed" signals while the selection list is open. To
> > change this behaviour we would have to subclass the combobox object and
> > surpress these signals unless there was an exising object property which
> > did this already. I'll look into the latter but if that turns out negative
> > this is probably something I won't look into at present as it's not really
> > a MOTU issue.
> > > The lines in the dial widgets are hard to see with my desktop
> > > configuration. I'm using KDE with the Plastik style.
> > Yes, the Qt dial widget is awful IMHO. Again, it's more a Qt problem than
> > anything else. Since I'm concentrating more on functionality at present I
> > won't look into this now. However, it is something which bugs me (and
> > probably others) too, so it'll probably be addressed by someone in due
> > course.
> > > It would be nice if you could double click on the dial widgets (e.g. Pan)
> > > and an edit box appears where you can enter the exact value. Ardour has
> > > this feature and it's quite handy. If you can achieve this in some other
> > > way, that would be cool too.
> > Agree. Again this is more a widget property so it will have to wait until
> > the basic functionality is there. However, it's a good suggestion and
> > something like that ought to be done.
> This would be rather advanced stuff... And when you know how to do the
> programming you are still fighting with other peoples expectations on how
> these things should look...
> In jackmix I do have custom widgets to do that (ie. look nicer than the qt
> ones). But I don't think it is in the scope of ffado2.0 to include these.
I agree - as I said the low-level functionality is clearly the most
important thing right now. For FFADO 2.0 I aim to have the basic
functionality and structure in place and proven. Then we can worry about
introducing nicer widgets. :-) There's not much point spending time on the
widgets until the underlying code structure is stable - that just creates