"Werner LEMBERG" <[email protected]> writes:

> ---
>
> ** [issues:#5555] \tweak no longer works with \tuplet**
>
> **Status:** New
> **Created:** Thu Sep 19, 2019 10:02 AM UTC by Werner LEMBERG
> **Last Updated:** Thu Sep 19, 2019 10:02 AM UTC
> **Owner:** nobody
> **Attachments:**
>
> -
> [2.19.83.png](https://sourceforge.net/p/testlilyissues/issues/5555/attachment/2.19.83.png)
> (2.9 kB; image/png)
> -
> [be39d353.png](https://sourceforge.net/p/testlilyissues/issues/5555/attachment/be39d353.png)
> (3.3 kB; image/png)
>
>
> ~~~~
> \version "2.21.0"
>
> \header { texidoc = "
> Using @code{\tweak} it is possible to control @code{\tuplet}.
>
> Here is a counterexample.  This is a serious regression; it works
> just fine with version 2.19.83.
> " }
>
> {
>   \tweak style #'dashed-line \tuplet 3/2 { g'4 g'8 }
> }
>
> % EOF
> ~~~~

It's not part of the stable branch as far as I can see, so no 2.20 deal
breaker.  This is quite likely
<https://sourceforge.net/p/testlilyissues/issues/5302/>

    Issue 5302/3: Let \tweak on event chords manipulate its elements

    This makes \tweak on event chords actually get heeded and creates
    reasonably predictable behavior by tweaking the rhythmic elements (but
    not chord-wide articulations).  It also passes tweaks transparently
    through music wrapper expressions (like transpositions, context
    changes and other).

    To achieve this, it creates and uses a get-tweakable-music function
    that will deliver a list of primary music expressions tweaks should be
    applied to.

    This function is also used in the definition of \once to decide when a
    warning for misapplication of \once might be called for.


and is a result of \tuplet's TimeScaledMusic expression being a music
wrapper.  This would require amending the get-tweakable-music function
to exclude TimeScaledMusic.

Somebody up to auditing the music types to see whether there are other
music-wrapper expressions that should not be pass-through for tweaks?

Or would it be better to maintain a blacklist of untweakable
music-wrappers rather than a whitelist of tweakable ones?

Or should tuplet cease to be a music-wrapper?  That may be the sanest
course since its bracketing action is really more than just a wrapper.

I think I'll make a patch along that line, but that does not mean that
the above-mentioned audit would be a bad idea.

-- 
David Kastrup


---

** [issues:#5555] \tweak no longer works with \tuplet**

**Status:** New
**Created:** Thu Sep 19, 2019 10:02 AM UTC by Werner LEMBERG
**Last Updated:** Thu Sep 19, 2019 10:02 AM UTC
**Owner:** nobody
**Attachments:**

- 
[2.19.83.png](https://sourceforge.net/p/testlilyissues/issues/5555/attachment/2.19.83.png)
 (2.9 kB; image/png)
- 
[be39d353.png](https://sourceforge.net/p/testlilyissues/issues/5555/attachment/be39d353.png)
 (3.3 kB; image/png)


~~~~
\version "2.21.0"

\header { texidoc = "
Using @code{\tweak} it is possible to control @code{\tuplet}.

Here is a counterexample.  This is a serious regression; it works
just fine with version 2.19.83.
" }

{
  \tweak style #'dashed-line \tuplet 3/2 { g'4 g'8 }
}

% EOF
~~~~


---

Sent from sourceforge.net because [email protected] 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.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto

Reply via email to