From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Beamer support - 2nd round Date: Mon, 7 Dec 2009 00:51:38 +0100 Message-ID: <31304B0C-2539-4E42-B6CC-CD2C07C18896@gmail.com> References: <87ljhi1tbo.wl%ucecesf@ucl.ac.uk> <98394494-D5E4-4C8E-BC6A-ECBFC7164DE6@gmail.com> <87vdgkcg0d.wl%ucecesf@ucl.ac.uk> Mime-Version: 1.0 (Apple Message framework v936) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NHQtK-0003d8-VF for emacs-orgmode@gnu.org; Sun, 06 Dec 2009 18:51:51 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NHQtG-0003ca-7K for emacs-orgmode@gnu.org; Sun, 06 Dec 2009 18:51:50 -0500 Received: from [199.232.76.173] (port=59149 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NHQtF-0003cS-U2 for emacs-orgmode@gnu.org; Sun, 06 Dec 2009 18:51:46 -0500 Received: from mail-ew0-f215.google.com ([209.85.219.215]:50744) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NHQtF-0006GX-Jl for emacs-orgmode@gnu.org; Sun, 06 Dec 2009 18:51:46 -0500 Received: by ewy7 with SMTP id 7so4580152ewy.32 for ; Sun, 06 Dec 2009 15:51:41 -0800 (PST) In-Reply-To: <87vdgkcg0d.wl%ucecesf@ucl.ac.uk> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric S Fraga Cc: emacs-orgmode Mode Hi Eric, On Dec 6, 2009, at 3:51 PM, Eric S Fraga wrote: > At Sat, 5 Dec 2009 18:10:33 +0100, > Carsten Dominik wrote: >>> - I need to be able to specify arguments for columns (i.e. the >>> environment, not specific columns), specifically >>> often [t] to make two columns align vertically >> >> Yes, this is a problem. YOu can specify arguments for the columns >> environment if you create it explicitly, i.e. with a headline with >> BEAMER_env set to "columns". But I can see that it would be good to >> be able to set an argument also when creating the environment >> implicitly. I'll think of something. > > Using an explicit environment is not a big deal but I couldn't get it > to work in this manner. Does it work for you? Try to columns that > are different heights. The default placement is to centre them > vertically which can look strange depending on their content. The [t] > allows for them to align at the top. Yep, this was a mistake in the template. Fixed now. > >>> - I don't understand what the difference between opt and envargs is. >>> In fact, I see no reference to BEAMER_opt in the document you wrote >>> yet your example has opt as one of the column view specifications. >> >> opt is obsolete, I had three separate properties opt, ovl, and dovl >> at some point (tried many different things during the last week), >> but I decided to lump them all into one, envargs. > > Makes sense. Thanks. > >>> - it would be nice if when a column heading is also a block heading, >>> that the tags generated (which, by the way, is a really nice >>> feature) include both block and column tags to make it easy to spot >>> the column aspect. >> >> Hmm, I agree that this would be useful. You mean if a heading has >> both >> BEAMER_env and BEAMER_col set.... > > Yes, exactly. OK, this works now as well. And you can pass options to the columns environment and to the column environment by preceeding [..] with "c" or "C", like this: * This is a frame ** Block starting also a column :BMCOL:B_block: :PROPERTIES: :BEAMER_env: block :BEAMER_envargs: [op-for-block] c[opt-for-column-env] C[opt-for- columns-env] :END: Not strongly tested, but I hope it works... - Carsten > > Thanks, > eric - Carsten