Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
Han-Wen Nienhuys wrote:
I want the syntax to reflect what Lily is doing inside. If you can
figure out a way to unify both types of properties internally, I will
unify the syntax.
Ideally, the user shouldn't need to know anything about the structur
[EMAIL PROTECTED] writes:
> Han-Wen Nienhuys wrote:
> > I want the syntax to reflect what Lily is doing inside. If you can
> > figure out a way to unify both types of properties internally, I will
> > unify the syntax.
>
> Ideally, the user shouldn't need to know anything about the structure
> of
Han-Wen Nienhuys wrote:
I want the syntax to reflect what Lily is doing inside. If you can
figure out a way to unify both types of properties internally, I will
unify the syntax.
Ideally, the user shouldn't need to know anything about the structure
of the implementation. If we need the separation,
[EMAIL PROTECTED] writes:
> > Yes - that's exactly the view I want to go away, because I think it
> > breeds confusion over what Lily is doing, and as a result, it makes
> > it harder to understand how to influence the formatting process.
>
> Really? Why do you think that confusion could arise?
On Sun, 15 Feb 2004 16:00:10 +0100 (CET) Werner LEMBERG <[EMAIL PROTECTED]> wrote:
> > > From a user's point of view, a property is a property.
> >
> > Yes - that's exactly the view I want to go away, because I think it
> > breeds confusion over what Lily is doing, and as a result, it makes
> > it
> > From a user's point of view, a property is a property.
>
> Yes - that's exactly the view I want to go away, because I think it
> breeds confusion over what Lily is doing, and as a result, it makes
> it harder to understand how to influence the formatting process.
Really? Why do you think that
[EMAIL PROTECTED] writes:
> You still don't understand me. I wonder why we need a different
> syntax for changing translation and layout properties.
> From a user's
> point of view, a property is a property.
Yes - that's exactly the view I want to go away, because I think it
breeds confusion o
> \set and \unset involve translation properties
> (eg. Score.measurePosition), while \override and \revert involve
> layout properties (eg. #'thickness, #'direction). If this doesn't
> clarify things, then you should read the LilyPond documentation,
> chapter Technical Manual.
You still don't u
[EMAIL PROTECTED] writes:
>
> > Read the release notes more carefully. Essentially, I have removed
> > the old-style \set. Now, \unset is the proper inverse of \set .
>
> I've read that -- excuse my ignorance, but I still don't get it.
> Assuming the new keywords, what is the actual difference?
> Read the release notes more carefully. Essentially, I have removed
> the old-style \set. Now, \unset is the proper inverse of \set .
I've read that -- excuse my ignorance, but I still don't get it.
Assuming the new keywords, what is the actual difference? What can
you do with \override what \s
[EMAIL PROTECTED] writes:
>
> > > What's the difference between \set and \override, except syntax?
> >
> > that they do entirely different things.
>
> Really? Please give an example where \set and \override do different
> things.
Read the release notes more carefully. Essentially, I have remov
> > What's the difference between \set and \override, except syntax?
>
> that they do entirely different things.
Really? Please give an example where \set and \override do different
things.
Werner
___
Lilypond-devel mailing list
[EMAIL PROTECT
[EMAIL PROTECTED] writes:
> > \property A.B \override #C = #D (removed)
> > \property A.B \revert #C \revert A.B #C
>
> What's the difference between \set and \override, except syntax? Why
that they do entirely different things. I think that another keyword
clarifi
On Sat, 14 Feb 2004, Werner LEMBERG wrote:
> >* The syntax for setting properties has been simplified: the
> > following table lists the differences:
> >
> >(old) (new)
> >
> > \property A.B = #C\set A.B = #C
> >
> \property A.B = #C\set A.B = #C
> \property A.B \unset \unset A.B
> \property A.B \set #C = #D\override A.B #C = #D
> \property A.B \override #C = #D (removed)
> \property A.B \revert #C \revert A.B
>* The syntax for setting properties has been simplified: the
> following table lists the differences:
>
>(old) (new)
>
> \property A.B = #C\set A.B = #C
> \property A.B \unset \unset A.B
>
16 matches
Mail list logo
