15 Aug
2004
15 Aug
'04
11:44 p.m.
Once again, I'm cross posting this to the users list in case anybody
is interested in fooling around with the demo apps.
I'm pleased to announce the release of PHAT, the Phat Audio Toolkit,
version 0.2.0. PHAT is a collection of GTK+ widgets that may prove
useful to audio applications.
New to this release is a shameless ripoff of Blender's "sliderbutton"
widgets. I like 'em more than regular GtkSpinButtons. Also, there
have been sundry improvements to the fansliders, and all widgets are
now mousewheelable and focusable, and they respond to sensitivity
changes (i.e. they're well behaved).
After installing, you'll have two demo apps at your disposal:
phatsliderbutton
phatfanslider
(A few) more details are available at www.gazuga.net/phat.php
Enjoy.
--
Pete
<http://www.gazuga.net>
"Nothing great was ever achieved by being realistic!" --Tom Venuto
17 Aug
17 Aug
1:44 p.m.
On Sun, 2004-08-15 at 21:28, Pete Bessman wrote:
Once again, I'm cross posting this to the users
list in case anybody
is interested in fooling around with the demo apps.
I'm pleased to announce the release of PHAT, the Phat Audio Toolkit,
version 0.2.0. PHAT is a collection of GTK+ widgets that may prove
useful to audio applications.
New to this release is a shameless ripoff of Blender's "sliderbutton"
widgets. I like 'em more than regular GtkSpinButtons. Also, there
have been sundry improvements to the fansliders, and all widgets are
now mousewheelable and focusable, and they respond to sensitivity
changes (i.e. they're well behaved).
I like the sliderbutton, but I think it'd be nicer and easier to read
with some kind of graphical representation of the value as well.
There's so much horizontal empty space there behind the text labels, why
not put a 'progress bar' in the background? That would make it really
nice for pan widgets etc.
As for the fanslider, it's a really cool idea, but way, way too flickery
on my machine to consider using.
-DR-
4:31 p.m.
Dave Robillard wrote on Tue, 17-Aug-2004:
I like the sliderbutton, but I think it'd be nicer
and easier to read
with some kind of graphical representation of the value as well.
There's so much horizontal empty space there behind the text labels, why
not put a 'progress bar' in the background? That would make it really
nice for pan widgets etc.
For an example of that see Ardour's widgets for panning and plugin
parameter controls. They work fairly well, a double click
will change the area into a text entry (spinner too) for direct
value entry. Holding control increases the resolution of change.
In fact the sliderbutton really just seems to lack the visual
indication of "sliderness", and i think adding it as Dave suggested
would be a good addition (or make a new widget).
jlc
6:12 p.m.
At Tue, 17 Aug 2004 14:15:30 -0400,
Jesse Chappell wrote:
In fact the sliderbutton really just seems to lack the visual
indication of "sliderness", and i think adding it as Dave suggested
would be a good addition (or make a new widget).
I have no idea what you mean by lacking a visual indication of
sliderness.
None of this is the point of the sliderbutton. I tend to think that
representing discrete numerical quantities (i.e. Channels 1 to 16) is
best done with the roman alphabet.
For the sliderbutton in graphical form with variable precision, check
the fansliders. Sorry about the flicker, it doesn't happen when
dragging to the right or down; the problems with up and left are due
to (AFAICS) insurmountable problems with X11. You can hold down ctrl
to freeze the fan at it's current size, which stops the flicker while
adjusting (also, shift freezes value adjustments so you can drag out
without screwing up the current value).
Basically, use the sliderbuttons when the number is important, use the
fansliders when it isn't.
--Pete
<http://www.gazuga.net>
"Nothing great was ever achieved by being realistic!" --Tom Venuto
6:25 p.m.
On Tue, 2004-08-17 at 15:56, Pete Bessman wrote:
At Tue, 17 Aug 2004 14:15:30 -0400,
Jesse Chappell wrote:
Fair enough.
In fact the sliderbutton really just seems to lack the visual
indication of "sliderness", and i think adding it as Dave suggested
would be a good addition (or make a new widget).
I have no idea what you mean by lacking a visual indication of
sliderness.
None of this is the point of the sliderbutton. I tend to think that
representing discrete numerical quantities (i.e. Channels 1 to 16) is
best done with the roman alphabet.
For the sliderbutton in graphical form with variable precision, check
the fansliders. Sorry about the flicker, it doesn't happen when
dragging to the right or down;
It doesn't flicker, but the rightmost edge is really jumpy and glitchy
looking. Maybe add a bit of a horizontal threshold for resizing so it
doesn't look so glitchy?
-DR-
7:10 p.m.
At Tue, 17 Aug 2004 16:11:07 -0400,
Dave Robillard wrote:
This is probably a good idea in general; I bet it would reduce the
flickeriness of the fans in general. It's Thorsten's baby, so I want
to wait until he chimes in before moving forward. However, I think if
the threshold is adjustable, this is a good feature to include.
--Pete
<http://www.gazuga.net>
"Nothing great was ever achieved by being realistic!" --Tom Venuto
Sorry about the flicker, it doesn't happen
when
dragging to the right or down;
It doesn't flicker, but the rightmost edge is really jumpy and glitchy
looking. Maybe add a bit of a horizontal threshold for resizing so it
doesn't look so glitchy?
7:27 p.m.
Pete Bessman wrote on Tue, 17-Aug-2004:
None of this is the point of the sliderbutton. I tend
to think that
representing discrete numerical quantities (i.e. Channels 1 to 16) is
best done with the roman alphabet.
OK, but I also see that the widget itself is capable of variable
non-discrete numerical quantities.
Basically, use the sliderbuttons when the number is
important, use the
fansliders when it isn't.
There are cases when both are important. Also, some people might
find the graphical fan invasive, but still want a graphical indication
as well as numerical one.
Sounds like a 3rd widget to me.
jlc
7344
days inactive
7346
days old
linux-audio-dev@lists.linuxaudio.org
6 comments
3 participants
participants (3)
-
Dave Robillard -
Jesse Chappell -
Pete Bessman