Hi Harm and Lukas,
thank you for this reference and minimal example. In fact the
ready-to-use example looks like I can directly apply it to my use case.
I must say I would have never thought of such an approach!
Best
Urs
Am 14.03.19 um 21:27 schrieb Lukas-Fabian Moser:
http://lsr.di.unimi
Hi all, this is more out of curiousity.
Markups can't flow beyond the end of a score (horizontally) and widen
the score if necessary:
\version "2.19.82"
{
c'1 -"This is a long text that widens the score because it can't protrude."
c'1
}
Is there a possibility to override this behaviour s
At 08:44 on 15 Mar 2019, Urs Liska wrote:
> Hi all, this is more out of curiousity.
>
> Markups can't flow beyond the end of a score (horizontally) and widen
> the score if necessary:
>
> \version "2.19.82"
>
> {
>c'1 -"This is a long text that widens the score because it can't protrude."
>
Hi,
I'm thinking about collecting some (and hopefully a growing corpus) of
the functions that help dealing with grobs in callback functions and
make them accessible in an openLilyLib package. For example for so many
applications it is necessary to find a grob's system, then get all
objects wi
Hi Urs,
Any good?
\version "2.19.82"
{
c'1
-\markup {
\with-dimensions #'(0 . 0) #'(2 . 0)
"This is a long text that widens the score because it can't protrude."
}
}
Andrew
On Fri, 15 Mar 2019 at 19:45, Urs Liska wrote:
> Hi all, this is more out of curiousity.
>
> Markups can
Hi Mark,
Am 15.03.19 um 10:08 schrieb Mark Knoop:
At 08:44 on 15 Mar 2019, Urs Liska wrote:
Hi all, this is more out of curiousity.
Markups can't flow beyond the end of a score (horizontally) and widen
the score if necessary:
\version "2.19.82"
{
c'1 -"This is a long text that widens the
Hi Andrew,
Am 15.03.19 um 10:14 schrieb Andrew Bernard:
\version "2.19.82"
{
c'1
-\markup {
\with-dimensions #'(0 . 0) #'(2 . 0)
"This is a long text that widens the score because it can't protrude."
}
}
Perfect! Both from the result and conceptually exactly what I was
looking
Il giorno ven 1 mar 2019 alle 21:14, David Wright
ha scritto:
Actually, I think there's an error in your reasoning in the apparmor
section, but I'm unable to test it because I have nothing installed
(that I know of) using these files. You wrote:
Next, edit '/etc/apparmor.d/usr.bin.evince' an
Hi Federico,
Well, the '#' issue was a simple typo, not a vast conceptual error.
I developed this on my pristine Ubuntu 18.10 and it all works swimmingly.
I am puzzled by your statement about need to be aware of different paths
for apparmor. This is system software and the location does not vary
Hi Urs, hi all,
sorry, I accidentally deleted the thread just before some hint came to
my mind, so this is not a "proper" reply.
\with-dimensions came to my mind as well, but it's not without
drawbacks. Somewhat more cumbersome to use, but also *somewhat* more
robust is to use a TextSpanner.
Il giorno ven 15 mar 2019 alle 14:31, Andrew Bernard
ha scritto:
Hi Federico,
Well, the '#' issue was a simple typo, not a vast conceptual error.
I developed this on my pristine Ubuntu 18.10 and it all works
swimmingly.
I am puzzled by your statement about need to be aware of different
Urs,
First, I’m new to LilyPond internals, so take everything I’m saying here with a
grain of salt. Please, someone correct me if I say something wrong.
When properties are set to a procedure instead of a value, we call that
procedure a callback. The callback is called whenever code
On Fri, Mar 15, 2019 at 4:13 AM Urs Liska wrote:
>
> Hi,
>
> I'm thinking about collecting some (and hopefully a growing corpus) of
> the functions that help dealing with grobs in callback functions and
> make them accessible in an openLilyLib package. For example for so many
> applications it is
On Sat 16 Mar 2019 at 00:31:16 (+1100), Andrew Bernard wrote:
> Hi Federico,
>
> Well, the '#' issue was a simple typo, not a vast conceptual error.
>
> I developed this on my pristine Ubuntu 18.10 and it all works swimmingly.
Then I don't understand why you were altering the line at all.
AFAICT
14 matches
Mail list logo
