[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5161 Announce slur ends when they are known
- Description has changed: Diff: - **Needs**: --> - **Type**: Enhancement --> Defect - **Comment**: Whenever I try actually using LilyPond for typesetting something of my own, I swear I have no idea how people can actually get anything done with it. --- ** [issues:#5161] Announce slur ends when they are known** **Status:** Started **Created:** Mon Jul 24, 2017 11:12 AM UTC by David Kastrup **Last Updated:** Mon Jul 24, 2017 11:12 AM UTC **Owner:** David Kastrup Announce slur ends when they are known Previously they were announced at the end of the time step, too late to actually run the process_acknowledged hook any more. This change makes it possible to end ongoing slurs in the end of a repeat alternative with <>) when they have been started with -\tweak to-barline ##t ( http://codereview.appspot.com/329880043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5161 Announce slur ends when they are known
--- ** [issues:#5161] Announce slur ends when they are known** **Status:** Started **Created:** Mon Jul 24, 2017 11:12 AM UTC by David Kastrup **Last Updated:** Mon Jul 24, 2017 11:12 AM UTC **Owner:** nobody Announce slur ends when they are known Previously they were announced at the end of the time step, too late to actually run the process_acknowledged hook any more. This change makes it possible to end ongoing slurs in the end of a repeat alternative with <>) when they have been started with -\tweak to-barline ##t ( http://codereview.appspot.com/329880043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Ticket 3609 discussion
Things are even worse if \start/stopStaff is happen at line-break, repeat-signs and different StaffSymbol.line-positions are used. ~~~ \paper { indent = 0 line-width = 40 } musII = { \repeat volta 2 { c'1 } %\workAround \break \stopStaff \override Staff.StaffSymbol.line-positions = #'(-6) \override Staff.Clef #'stencil = ##f \startStaff \repeat volta 2 { c'1 } } \new StaffGroup << \new Staff \musII \new Staff \musII ~~~ See attached png. A workaround for the Barline could be: ~~~ workAround = \once \override Staff.BarLine #'before-line-breaking = #(lambda (grob) (if (eqv? LEFT (ly:item-break-dir grob)) (begin (ly:grob-set-property! grob 'bar-extent '(-5 . -1)) (ly:grob-set-property! grob 'Y-extent '(-5 . -1)) (ly:grob-set-property! grob 'Y-offset 3 ~~~ Still no SpanBar, that's issue 2876, though. Attachments: - [atest-63-1.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/42f48c44/d912/attachment/atest-63-1.png) (8.8 kB; image/png) --- ** [issues:#3609] \stopStaff at the end of a measure should produce a bar line spanning the previous staff lines** **Status:** Accepted **Created:** Sun Oct 13, 2013 03:09 PM UTC by Anonymous **Last Updated:** Sun Oct 13, 2013 03:09 PM UTC **Owner:** nobody *Originally created by:* *anonymous *Originally created by:* [elu...@gmail.com](http://code.google.com/u/114137843947982417046/) several uglies have been discussed in this thread [http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-td152072.html](http://lilypond.1069038.n5.nabble.com/ugly-bar-line-when-changing-line-count-td152072.html) 1\. the main outline is that a \stopStaff \startStaff doesn't terminate "correctly" a measure with a staff-bar covering the full line-count of the preceding measure but just spans the line-count of the following code. 2\. when a time signature change \(or key or clef\) occurs the staff lines of the preceding and following measure overlap. 3\. if there are accidentals involved they are not clearly separated from the preceding part workarounds are presented in the link above but the majority of the participants to the discussion \(66:33%\) vote for a clean LilyPond integrated solution - and honestly I'd also appreciate if this would happen automatically. --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto