Re: Allow specifying different alignment for grob and its parent (issue 118950043 by address@hidden)

[janek . lilypond]

Pushed as two commits (to differentiate between new functionality and
restoring old behaviour):

commit d7b067b15ae975ee52f91bd674cc667baa09eb04
Author: Janek Warchoł <address@hidden>
Date:   Sat Aug 9 21:08:08 2014 +0200

    Grob alignment: get back 2.19.9 behaviour

    A series of commits

    *   0bc7f77 Issue 3978: Merge alignment cleanup
    |\
    | * d6604b0 define-grobs.scm: reorder properties alphabetically
    | * 6f3f8f0 TextScript, CombineTextScript: use aligned_on_parent
    | * 1d76502 Replace XY-offset closures with aligned_on_parent where
possible
    | * 09412c2 Clean up DynamicText horizontal alignment.
    |/

    changed how some grobs (notably DynamicTexts) reacted to overriding
    self-alignment-X property.  The new behaviour was confusing for some
    users, so this commit gets back the old behaviour.  The possibility
    of using separate alignment factors for grob and its parent,
introduced
    by previous commit (see Issue 4022), makes it possible to get
pre-0bc7f77
    behaviour just by changing default values of parent-alignment-*;
leaving
    up the possibility to easily change them in the future.

    See
http://lists.gnu.org/archive/html/lilypond-user/2014-07/msg00691.html
    and https://code.google.com/p/lilypond/issues/detail?id=4036
    for details.

commit 0c4f221e5d4656abd47f067907611df200fbfc20
Author: Janek Warchoł <address@hidden>
Date:   Sun Jul 20 20:07:16 2014 +0200

    Issue 4022: Allow specifying different alignment for grob and its
parent

    This gives users more possibilities for grob positioning - for
example,
    they can align left edge of a grob on center of its parent, etc.

    Also fix Issue 4054.


https://codereview.appspot.com/118950043/