Greetings Bug Squad,
Currently the function "make-connected-path-stencil"[1] does not allow you to
specify the starting point (origin) of the path, but arbitrarily hard-codes it
as (0 0). This makes the function less flexible for no good reason.
(Well, at least none that I can see, unless for
Greetings Bug Squad,
Currently the function "make-connected-path-stencil"[1] does not allow you to
specify the starting point (origin) of the path, but arbitrarily hard-codes it
as (0 0). This makes the function less flexible for no good reason.
(Well, at least none that I can see, unless for
0.15
1.1
1.1
#f
#f)
}
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/make-connected-path-stencil-should-not-hard-code-the-path-origin-at-0-0-tp152879p152880.html
Sent from the Bugs mailing list archive at Nabble.com.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
> Paul Morris wrote:
> Currently the function "make-connected-path-stencil"[1] does not allow you to
> specify the starting point (origin) of the path, but arbitrarily hard-codes
> it
> as (0 0). This makes the function less flexible for no good reason.
Hello bug squad,
I'd like to withdraw
