From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - tools 0001664]: GTK2-patch for envy24control
Date: Wed, 18 Jan 2006 21:59:05 +0100 [thread overview]
Message-ID: <234f8cf39f9bee3023ca2a9ea2dffba1@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1664>
======================================================================
Reported By: electropura
Assigned To:
======================================================================
Project: ALSA - tools
Issue ID: 1664
Category: envy24control
Reproducibility: N/A
Severity: feature
Priority: normal
Status: new
======================================================================
Date Submitted: 12-21-2005 01:56 CET
Last Modified: 01-18-2006 21:59 CET
======================================================================
Summary: GTK2-patch for envy24control
Description:
Here is a simple patch to make it convenient to link envy24control against
GTK2.
This is essentially from a patch I found via google some year ago. I can't
find it anymore, so I don't know who made it in the first place.
I also changed the policy for scrolled windows from GTK_POLICY_ALWAYS to
GTK_POLICY_AUTOMATIC. This makes it look much nicer with cards that have
fewer channels (like m-audio audiophile).
======================================================================
----------------------------------------------------------------------
HaroldAling - 01-18-06 21:49
----------------------------------------------------------------------
This is great!
I just needed to remove the alsa-tools/ prefix since the alsa-tools
package unpacks in alsa-tools-1.0.10/.
I'm about to file a bug(/featurerequest) in bugs.gentoo.org to get this
patch included into portage...
ALSA-devs: when is this going into the alsa-tools package???
----------------------------------------------------------------------
HaroldAling - 01-18-06 21:59
----------------------------------------------------------------------
And I just did: http://bugs.gentoo.org/show_bug.cgi?id=119478
Issue History
Date Modified Username Field Change
======================================================================
12-21-05 01:56 electropura New Issue
12-21-05 01:56 electropura File Added: envy24control-gtk2.patch
01-18-06 21:49 HaroldAling Note Added: 0007713
01-18-06 21:59 HaroldAling Note Added: 0007714
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next reply other threads:[~2006-01-18 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 20:59 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 11:22 [ALSA - tools 0001664]: GTK2-patch for envy24control bugtrack
2006-01-20 7:02 bugtrack
2006-01-18 22:21 bugtrack
2006-01-18 22:18 bugtrack
2006-01-18 20:49 bugtrack
2005-12-21 0:56 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=234f8cf39f9bee3023ca2a9ea2dffba1@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.