From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Seiji Zenitani Newsgroups: gmane.emacs.devel Subject: Re: Adding parameters to windows Date: Tue, 03 Jun 2008 05:04:14 -0400 Message-ID: References: <5E334A4B-4D42-49E9-A05D-FFD689BD59B7@mac.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7BIT X-Trace: ger.gmane.org 1212484112 28001 80.91.229.12 (3 Jun 2008 09:08:32 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 3 Jun 2008 09:08:32 +0000 (UTC) Cc: Stefan Monnier To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 03 11:09:14 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K3SVw-0006dP-0U for ged-emacs-devel@m.gmane.org; Tue, 03 Jun 2008 11:09:08 +0200 Original-Received: from localhost ([127.0.0.1]:52698 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3SV9-0006Sp-Jn for ged-emacs-devel@m.gmane.org; Tue, 03 Jun 2008 05:08:19 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K3SRN-0004PS-E7 for emacs-devel@gnu.org; Tue, 03 Jun 2008 05:04:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K3SRL-0004OR-89 for emacs-devel@gnu.org; Tue, 03 Jun 2008 05:04:24 -0400 Original-Received: from [199.232.76.173] (port=34588 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3SRK-0004O7-4Q for emacs-devel@gnu.org; Tue, 03 Jun 2008 05:04:22 -0400 Original-Received: from smtpoutm.mac.com ([17.148.16.67]:50792) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1K3SRJ-00033u-L8 for emacs-devel@gnu.org; Tue, 03 Jun 2008 05:04:21 -0400 Original-Received: from smtpin124.mac.com (smtpin124-bge351000 [10.150.68.124]) by smtpoutm.mac.com (Xserve/smtpout004/MantshX 4.0) with ESMTP id m5394Jml019629 for ; Tue, 3 Jun 2008 02:04:19 -0700 (PDT) Original-Received: from [10.0.1.200] (c-98-218-103-81.hsd1.md.comcast.net [98.218.103.81]) by smtpin124.mac.com (Sun Java(tm) System Messaging Server 6.3-6.03 (built Mar 14 2008; 32bit)) with ESMTPA id <0K1V00FITQJ55Z80@smtpin124.mac.com> for emacs-devel@gnu.org; Tue, 03 Jun 2008 02:04:19 -0700 (PDT) In-reply-to: X-Mailer: Apple Mail (2.924) X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (1) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:98292 Archived-At: Hi, I noticed that the transparency code was already installed. Here is a NEWS entry for it. Thanks, Seiji ** Frame operations: *** Controlling the frame opacity. The opacity of a frame can now be controlled by setting the `alpha' frame parameter, on X Window system with composite extension. The alpha parameter should be an integer between 0 (transparent) and 100 (opaque) or a float number between 0.0 and 1.0. Optionally, the opacity can be set by a cons cell; the first item controlls the opacity of an active frame, and the second item controlls that of non-active frames. (set-frame-parameter nil 'alpha 80) (set-frame-parameter nil 'alpha 0.8) (set-frame-parameter nil 'alpha '(100 70)) ;; ( []) (set-frame-parameter nil 'alpha nil) Note that the threshold opacity of a frame is defined by the variable `frame-alpha-lower-limit', so that the user may not lose control of the frame. The default value is 20. Similarly, an integer (0-100) or a float number (0.0-1.0) can be set. On 2008/05/19, at 21:17, Stefan Monnier wrote: >>> Now that your copyright papers are on file, could you send us >>> a patch together with a corresponding ChangeLog entry? > >> Here's a patch & ChangeLog lines for a new frame parameter. > > It looks OK. Whoever decides to instll it just needs to make the > following adjustments: > 1 - follow coding conventions (a space after ";" and ",", a space > around binary operators). > 2 - add a NEWS entry and a ChangeLog entry. > > > Stefan