On Fri, Feb 7, 2020 at 4:28 AM Aaron Hill wrote:
> I have applied this logic to your code and made some changes [1].
>
> [1]: http://lilybin.com/bt0t2d/11
>
>
That's great, Aaron!
Now we have a very robust method for *easy* spacing *complex* vertical
layouts.
I would not even consider this a
On 2020-02-06 3:02 pm, Paolo Prete wrote:
On Thu, Feb 6, 2020 at 6:04 PM Aaron Hill
wrote:
On 2020-02-06 8:35 am, Paolo Prete wrote:
> I ask you if is it possible to remove the noisy default #OSSPW param
> as
> well, in the function call.
Also: I'm seeing that it compiles well on 2.19.45
On Thu, Feb 6, 2020 at 6:04 PM Aaron Hill wrote:
> On 2020-02-06 8:35 am, Paolo Prete wrote:
> > I ask you if is it possible to remove the noisy default #OSSPW param
> > as
> > well, in the function call.
>
>
Also: I'm seeing that it compiles well on 2.19.45 (lilybin) but doesn't
compile on
On Thu, Feb 6, 2020 at 6:04 PM Aaron Hill wrote:
>
> Another option would be to accept height and width in the same argument
> using a custom type predicate:
>
>
Thanks again. Here's the _complete_ version.
http://lilybin.com/bt0t2d/10
I find it *very* useful. In this way you can easily add a
On 2020-02-06 8:35 am, Paolo Prete wrote:
I ask you if is it possible to remove the noisy default #OSSPW param
as
well, in the function call.
Default arguments cannot be in the final position, which is why you have
to specify the value.
Consider whether you can reorder arguments or add an
On Thu, Feb 6, 2020 at 4:45 PM Aaron Hill wrote:
> On 2020-02-06 6:10 am, Paolo Prete wrote:
> > (code)
>
> A few comments on the code:
>
>
Good, thanks
Here's the improved version without the noisy syntax and better names (OS =
Outside Staff)
I ask you if is it possible to remove the noisy
On 2020-02-06 6:10 am, Paolo Prete wrote:
(code)
A few comments on the code:
1) "begin" is used to specify multiple expressions in a construct that
only accepts one. "if" would be an example where "begin" could be
useful; but "let", like many other constructs, already accepts a list of
Hi Andrew,
What I want to achieve is to obtain a template for easy spacing objects
vertically. This spacing is very hard to achieve when there are many layers
of objects. And it becomes even harder when you realize that you have to
change the order of the positions. Instead, with my system, I
Hello Paolo,
What are you trying to achieve?
Andrew
On Thu, 6 Feb 2020 at 11:48, Paolo Prete wrote:
> I just had this idea about a *new* method of spacing.
Hello,
I just had this idea about a *new* method of spacing.
Maybe this is nuts, and it's almost a hack, but I'm seeing that it could
work, so, please, leave me a feedback.
The idea is create an invisible "obstacle", with a length set in
staff-space units, between grobs.
Then, assign a position
10 matches
Mail list logo
