Rune Zedeler <[EMAIL PROTECTED]> writes:
> Oh, it's so easy when you know where to look :)
Good to hear that (the part about easy, that is) :)
> However, the following command looks like ... eh ... spaghetti... Does
> it really take so much to increase a value a bit?
Yes, I'm afraid it does.
> inf.elem_l_->set_grob_property ("arch-height",
> gh_double2scm(gh_scm2double(inf.elem_l_->get_grob_property
> ("arch-height"))+0.5));
There's not much you can do: you need to get the value from scheme,
and write it back. Note that while doing this, you're actually not
increasing the value proper. Rather, you're reading from the grob's
immutable_property_alist_, and putting an increased value on the
grob's mutable_propertly_alist_. In most cases, grobs share most of
their settings (from grob-description.scm), it is only when values are
changed or added, that extra memory is allocated for that grob.
It would be nice if this could be written in a scheme shorthand, though.
> By the way, all yhis manual copy-rename-diff-stuff makes me crazy; and
> sometimes sooner or later it'll surely end up with me mistakedly
> deleting some new sourcecode of mine...
> How do you guys do sending patches?
Ouch. You're the second one to ask since the doco for this was
removed. We edit the file VERSION, adding our own patchlevel (eg,
jcn1), and type
make release
which, with the correct setup in makes a tarball in ../releases, and a
patch in ../patches. It is a shorthand for make dist, make diff.
Also try `make help'. You can read about this at an old webpage:
http://appel.lilypond.org/lilypond/links/lilypond-1.3.125/Documentation/user/out-www/lilypond/Making-patches.html
[Han-Wen: please put the doco about this back in, somewhere?]
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
Gnu-music-discuss mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/gnu-music-discuss
