Werner LEMBERG writes:
>> Well, System::post_processing ends by creating the stencils of a
>> system in reverse order. That's probably not helping.
>
> A bug?
No, there is no guaranteed order of stencilization. But making stuff
more random gratuitously is still going to annoy
On Sun, Nov 22, 2015 at 2:44 PM, David Kastrup wrote:
> Thomas Morley writes:
>
> > Though, why it is that arbitrary?
> >
> > Look at this variation and the attached image:
> >
> > \version "2.19.29"
> > #(define test-nmbrs
> > (let ((nmbrs
David Nalesnik writes:
> My question would be: when does the evaluation of a grob's stencil
> normally happen? My guess is this normal evaluation is happening
> based on a haphazard input, that using 'before-line-breaking and
> 'after-line-breaking is forcing a later
On Sun, Nov 22, 2015 at 4:56 PM, David Kastrup wrote:
> David Nalesnik writes:
>
> > The following function gives each TextScript grobs on a line a number
> based
> > on its position within the 'all-elements array. Each line should be
> > numbered 1-20
David Nalesnik writes:
> The following function gives each TextScript grobs on a line a number based
> on its position within the 'all-elements array. Each line should be
> numbered 1-20 in order, but that's clearly not the case. There's a binding
> of texts which
> Well, System::post_processing ends by creating the stencils of a
> system in reverse order. That's probably not helping.
A bug?
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Hi,
On Sun, Nov 22, 2015 at 3:00 PM, David Kastrup wrote:
> Simon Albrecht writes:
>
> > On 22.11.2015 21:44, David Kastrup wrote:
> >> Thomas Morley writes:
> >>
> >>> Though, why it is that arbitrary?
> >>>
> >>> Look at this
On Sun, Nov 22, 2015 at 2:18 PM, David Nalesnik
wrote:
>
>
> On Sun, Nov 22, 2015 at 2:15 PM, Thomas Morley
> wrote:
>
>> 2015-11-22 20:49 GMT+01:00 David Nalesnik :
>> >
>> >
>> > On Sun, Nov 22, 2015 at 1:21 PM,
On Sun, Nov 22, 2015 at 1:21 PM, David Kastrup wrote:
>
> > Is there any way to get the override to be reevaluated with each repeat?
>
> No. Written in that manner, the override is evaluated at _input_ time.
> If you put it in a variable and use that variable 3 times, the colors
>
2015-11-22 20:49 GMT+01:00 David Nalesnik :
>
>
> On Sun, Nov 22, 2015 at 1:21 PM, David Kastrup wrote:
>>
>>
>> > Is there any way to get the override to be reevaluated with each repeat?
>>
>> No. Written in that manner, the override is evaluated at
On Sun, Nov 22, 2015 at 2:15 PM, Thomas Morley
wrote:
> 2015-11-22 20:49 GMT+01:00 David Nalesnik :
> >
> >
> > On Sun, Nov 22, 2015 at 1:21 PM, David Kastrup wrote:
> >>
> >>
> >> > Is there any way to get the override to be
Hi,
Given the following function, each time an override of NoteHead.color
occurs, a new color from the list is used:
\version "2.19.30"
#(define test
(let ((colors (circular-list red green blue yellow darkgreen magenta)))
(lambda ()
(let ((color (car colors)))
(set!
David Nalesnik writes:
> Hi,
>
> Given the following function, each time an override of NoteHead.color
> occurs, a new color from the list is used:
>
> \version "2.19.30"
>
> #(define test
>(let ((colors (circular-list red green blue yellow darkgreen magenta)))
>
Thomas Morley writes:
> Though, why it is that arbitrary?
>
> Look at this variation and the attached image:
>
> \version "2.19.29"
> #(define test-nmbrs
> (let ((nmbrs (circular-list 1 2 3 4)))
> (lambda (grob)
> (let ((n (car nmbrs)))
> (set! nmbrs
On 22.11.2015 21:44, David Kastrup wrote:
Thomas Morley writes:
Though, why it is that arbitrary?
Look at this variation and the attached image:
\version "2.19.29"
#(define test-nmbrs
(let ((nmbrs (circular-list 1 2 3 4)))
(lambda (grob)
(let ((n
Simon Albrecht writes:
> On 22.11.2015 21:44, David Kastrup wrote:
>> Thomas Morley writes:
>>
>>> Though, why it is that arbitrary?
>>>
>>> Look at this variation and the attached image:
>>>
>>> \version "2.19.29"
>>> #(define test-nmbrs
>>>
16 matches
Mail list logo