Re: Using Scheme

[Trent Johnston]

Sorry I should have been a bit more specific before...

I tried using

manBeam = #(define-music-function (parser location beg end) (number?
number?)
 #{ \once \override Beam #'positions = #'($beg . $end) #} )

but whenever I try to use it

\manBeam #6 #6  --- I get or any other possible combinations

"ERROR: Wrong type (expecting real number): lilyvartmpb"

>From what I can piece together from the documentation and the user-list I
think there is something more I need to do.. but can't figure that out.

Trent

----- Original Message ----- 
From: "Paul Scott" <address@hidden>
To: "Trent Johnston" <address@hidden>
Cc: <address@hidden>
Sent: Friday, May 12, 2006 7:23 PM
Subject: Re: Using Scheme


| Trent Johnston wrote:
| > Thanks for your help Paul, but I was actually looking at Beam settings
| >
| > a way to simplify \once \override Beam #'positions = #'( number .
number )
| >
| I understood that.
| > I used the padText as an example but couldn't get it to work with the
above
| > example...
| >
| I didn't have a quick application like yours to test since haven't used
| beam settings but I was just trying to help you understand how variables
| work so you could create your 'posBeam' (or whatever you want to call
| it) definition from the padText example.
|
| A quick attempt (completely untested) would be
|
|      posBeam = #(define-music-function (parser location num1 num2)
(number? number?)
|      #{
|        \once \override Beam #'position = #'( $num1 . $num2 )
|      #})
|
| Without testing I don't know whether you would apply it as:
|
| \posBeam #3 #2
| or
| \posBeam ( #3 . #2 )
| or something different.
|
| Paul
|
|