Updates:
Status: Verified
Comment #3 on issue 1751 by philehol...@googlemail.com: Most analysis
brackets get incorrect event-cause info, breaking point-and-click \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
(No comment was entered for this change
Updates:
Status: Fixed
Labels: fixed_2_15_5 backport
Comment #1 on issue 1751 by n.putt...@gmail.com: Most analysis brackets get
incorrect event-cause info, breaking point-and-click \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
Updates:
Labels: -backport backported fixed_2_14_2
Comment #2 on issue 1751 by carl.d.s...@gmail.com: Most analysis brackets
get incorrect event-cause info, breaking point-and-click \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
Backported, with commits
Status: Started
Owner: n.putt...@gmail.com
Labels: Type-Defect Priority-Medium
New issue 1751 by n.putt...@gmail.com: Most analysis brackets get incorrect
event-cause info, breaking point-and-click \tweak
http://code.google.com/p/lilypond/issues/detail?id=1751
Since
Hi,
may it be possible that the analysis brackets options do not work at all?
I tried to use straight brackets representing slurs in renaissance music - but
the bracket-flare parameter seemed to have no effect on the brackets. -
Thanks in advance for any help you might offer!
Yours,
D. Stoltz
On 2/16/07, D. Stoltz [EMAIL PROTECTED] wrote:
Hi,
may it be possible that the analysis brackets options do not work at all?
I tried to use straight brackets representing slurs in renaissance music - but
the bracket-flare parameter seemed to have no effect on the brackets. -
Thanks in advance
Is this really how it's supposed to work? The below code puts a bracket over
a b c and not only over b c as expected.
\version 2.7.10
\new Staff \with { \consists Horizontal_bracket_engraver }
\relative c'' { a \startGroup b c \stopGroup d }
--
Sven Axelsson
On 27-Sep-05, at 5:46 AM, Sven Axelsson wrote:
Is this really how it's supposed to work? The below code puts a
bracket over a b c and not only over b c as expected.
Remember that lilypond is almost all postfix notation. :)
(think of the behavior of a slur or beams)
Cheers,
- Graham
