On Thursday 04 May 2006 06:21, Arjan Bos wrote:
> Erik,
>
> That's a great document! I've read about half of it now and it does a
> very good job to explain to me how LilyPond works. And seeing the
> date on the title page, I think I have to congratulate you on your
> Masters Degree! Well Done!
Th
Erik,
That's a great document! I've read about half of it now and it does a
very good job to explain to me how LilyPond works. And seeing the
date on the title page, I think I have to congratulate you on your
Masters Degree! Well Done!
Off topic, but are your music streams implemented in
Quoting Michael Brennan <[EMAIL PROTECTED]>:
My simple understanding of it is that:
\set sets a property for the whole context, and the objects contained
in that context while
\override is for a particular graphical object.
Just a little explanation like that, that separates them would be
Erik Sandberg wrote:
Great! You now officially know more about this area than me, because I
don't have a clue when to use \override or \set. Please take a few
minutes to send me some clarifications or additions for the manual:
http://lilypond.org/web/devel/participating/documentation-adding
"grob" is just a silly abbreviation for graphical object. On one hand,
David is absolutely right that far too much of the implementation
structure is visible in the user interface. On the other hand, unless
the current approach to
do settings in LilyPond is revised completely, each user who
wan
> Hm. Here's my understanding of it:
>
> You can say it's all about the granularity of the setting. \override
> manipulates
> settings which are specific to one graphical object/grob (e.g. a NoteHead).
> \set
> changes settings on a higher level, and can modify more than one type of
> grob.
There
On 4/27/06, Rick Hansen (aka RickH) <[EMAIL PROTECTED]> wrote:
>
> Whats a grob?
I agree. The user absolutely should not have to know that there is
any such thing.
David
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailma
Whats a grob?
--
View this message in context:
http://www.nabble.com/Set-vs.-Override---I%27m-confused-t1433228.html#a4124826
Sent from the Gnu - Lilypond - User forum at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists
Citerar Graham Percival <[EMAIL PROTECTED]>:
>
> On 26-Apr-06, at 10:36 PM, Michael Brennan wrote:
>
> > David Feuer wrote:
> >> On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
> >>> In 2.8 there's an essential difference between grob and context
> >>> properties,
> >>> which is visible fo
Citerar Tomas Valusek <[EMAIL PROTECTED]>:
> Hello,
>
> > When I first read the manual I didn't see any clear explanation of the
> > difference,
> > the docs could be more clear on that point. But when I realized that one
> > was for grobs
> > and the other for context, it became much clearer,
On 27-Apr-06, at 2:20 AM, Mats Bengtsson wrote:
For some time, I have been thinking about adding an introductory text
to
the Changing Defaults chapter, which introduces all the main methods
to set context and grob properties with one example for each and links
to the more detailed sections.
For some time, I have been thinking about adding an introductory text to
the Changing Defaults chapter, which introduces all the main methods
to set context and grob properties with one example for each and links
to the more detailed sections. This would be something along the lines of
http://list
Hi,
I too find the context/grob property distinction not clear and I did not
find the online doc any help in getting through this barrier of
understanding. It is the one most powerful aspect of Lilypond, but the
one aspect which is treated the most meanly in the introductory docs.
Even user doing b
On 26-Apr-06, at 10:36 PM, Michael Brennan wrote:
David Feuer wrote:
On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
In 2.8 there's an essential difference between grob and context
properties,
which is visible for end-users: the \tweak command only makes sense
on layout
object propertie
Hello,
When I first read the manual I didn't see any clear explanation of the
difference,
the docs could be more clear on that point. But when I realized that one
was for grobs
and the other for context, it became much clearer, for me it helps
separating and understanding
grobs and contexts.
> [...] when I realized that one was for grobs and the other for
> context, it became much clearer, for me it helps separating and
> understanding grobs and contexts.
A big help would be a simple means to distinguish grobs and context
properties. For example, context property names could always
David Feuer wrote:
On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
In 2.8 there's an essential difference between grob and context properties,
which is visible for end-users: the \tweak command only makes sense on layout
object properties, not on context properties. This difference migh
> > In 2.8 there's an essential difference between grob and context properties,
> > which is visible for end-users: the \tweak command only makes sense on
> > layout
> > object properties, not on context properties. This difference might make it
> > easier for new users to understand grob properti
> > In 2.8 there's an essential difference between grob and context
> > properties, which is visible for end-users: the \tweak command
> > only makes sense on layout object properties, not on context
> > properties. This difference might make it easier for new users to
> > understand grob properti
On 4/19/06, Erik Sandberg <[EMAIL PROTECTED]> wrote:
> In 2.8 there's an essential difference between grob and context properties,
> which is visible for end-users: the \tweak command only makes sense on layout
> object properties, not on context properties. This difference might make it
> easier
On Tuesday 11 April 2006 23:56, Werner LEMBERG wrote:
> > \set: set the value of a context property
> > \override: set the value of a layout object property
>
> I've always wondered why it isn't possible to unify them...
In 2.8 there's an essential difference between grob and context properties,
Werner LEMBERG writes:
>> \set: set the value of a context property
>> \override: set the value of a layout object property
>
> I've always wondered why it isn't possible to unify them...
Or until that time have explicit naming.
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - Th
> \set: set the value of a context property
> \override: set the value of a layout object property
I've always wondered why it isn't possible to unify them...
Werner
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailma
Quoting Geoff Horton <[EMAIL PROTECTED]>:
The followup question is obvious, but I leave it to you to think about it
and see if you get any further.
I've been wondering for some time if the distinction is a helpful one,
but I suspect changing it now would involve too much internal
tinkering, no
> The followup question is obvious, but I leave it to you to think about it
> and see if you get any further.
I've been wondering for some time if the distinction is a helpful one,
but I suspect changing it now would involve too much internal
tinkering, not to mention breaking of old scores.
Geof
\set: set the value of a context property
\override: set the value of a layout object property
The followup question is obvious, but I leave it to you to think about it
and see if you get any further.
/Mats
Tomas Valusek wrote:
Hello,
I've read thoroughly LilyPond's Users Manual and I don'
Hello,
I've read thoroughly LilyPond's Users Manual and I don't understand
what's the difference between \set and \override commands. Can someone
explain me this? Thank you.
Tomas Valusek
___
lilypond-user mailing list
lilypond-user@gnu.org
http:/
27 matches
Mail list logo
