<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I have done a bit more research on the "Slur Tips Avoid Staff Lines"
issue and can confirm that "CalcLeft/RightEntryMetricsPos" always
returns the value that will be printed to PDF/printer.<br>
But: that value may differ from what is visible on the screen. <br>
If the slur touches the top or bottom staff line, the visual result
and the calculated values can be different.<br>
If the slur touches an inner staff line, the visual resuls and the
value were always identical (at least in my research).<br>
The visual appearance is also dependent on the current zoom
selection! With some zoom factors the staff line collision is
avoided, with some it isn't. There is probably a rounding problem
somewhere.<br>
<br>
Or in other words: I may see a collision for example between a slur
and expression on screen, but it will print fine without collision.<br>
<br>
I have also contacted MM on that issue, but their answer was neither
really helpful, nor really reproduceable - the screenshots they sent
looked different on my system. And even an identical slur sometimes
touches the stafflines and sometimes doesn't (see my attached
screenshot).<br>
<br>
MM wrote:<br>
"Tips Avoid Staff Lines workings in a contextual sense. It depends
on how many notes are under the slur and where the slur falls on the
page. It will not work on every instance of every slur due to how
each slur is created.<br>
Wide slurs will be more responsive to the avoid staff lines option,
small slurs won't be.<br>
It sounds like this feature is not described well in the manual, and
also may not be working the best."<br>
<br>
Not very satisfying, but at least the printed result is fine.<br>
<br>
Jan<br>
<br>
<br>
<div class="moz-cite-prefix">Am 16.11.2016 um 10:38 schrieb Jan
Angermüller:<br>
</div>
<blockquote
cite="mid:e1ddbbc6-0385-3c10-0393-f506b2a872ae@angermueller.com"
type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
>I think that CalcRightEntryMetricsPos is always correct<br>
><span id="result_box" class="short_text" lang="en"><span
class="">But Finale does not always display the values </span></span><span
id="result_box" class="short_text" lang="en"><span class=""><span
id="result_box" class="" lang="en"><span class=""> of</span></span></span></span><span
id="result_box" class="short_text" lang="en"><span class=""><span
id="result_box" class="" lang="en"><span class=""><span
id="result_box" class="short_text" lang="en"><span
class=""> "Smart shape placement"</span></span> .<br>
That's another possible perspective. And yes indeed, the
behaviour of "Tips Avoid Staff Lines" seems unclear to me
too and doesn't do what it promises to do. So probably
it's even recommended to uncheck this feature in the
options then.</span></span></span></span><br>
<br>
Jan<br>
<br>
<blockquote
cite="mid:2e4c5048-0219-b6fa-0ed3-56b6c28413f5@gmail.com"
type="cite">Le 16/11/2016 à 10:10, Jan Angermüller a écrit :<br>
<blockquote
cite="mid:78458da6-6e59-6513-6e4f-ec0819d3c947@angermueller.com"
type="cite">Hi Chris and Jari,<br>
<br>
<span id="result_box" class="short_text" lang="en"><span
class=""><span id="result_box" class="" lang="en"><span
class="">>The values of</span></span></span></span><span
id="result_box" class="short_text" lang="en"><span class=""><span
id="result_box" class="" lang="en"><span class=""><span
id="result_box" class="short_text" lang="en"><span
class=""> "Smart shape placement"</span></span>
are not always those displayed</span></span>.</span></span><br>
<span id="result_box" class="short_text" lang="en"><span
class="">>They depend on the parameter "Smart Slur
Options -> Tips avoid Staff Lines By".</span></span><br>
That's the solution!<br>
Although the interesting thing in this case is that the values
of "Smart Shape Placement" are indeed correct here (it's a 12
EVPU distance).<br>
It's only the calculated distance
(FCSmartShape:CalcRightEntryMetricsPos) that returns the wrong
value.<br>
But if I add the "Avoid Staff Lines" value to the wrong value,
it becomes correct. <br>
Or: if I set the "Avoid Staff Lines" value to 0 (which doesn't
change the slur visually), the calculated vertical metrics
from CalcRightEntryMetricsPos are also correct.<br>
<br>
So there must be a problem somewhere back in JW Lua or in the
Plugin SDK that<b> accidentally adds the Avoid Stafff Lines
values in this case.</b><br>
<br>
My workaround now: uncheck "Tips Avoid Staff Lines" or set the
value to 0.</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
JWLua mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:JWLua@jwmusic.nu">JWLua@jwmusic.nu</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu">http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
JWLua mailing list
<a class="moz-txt-link-abbreviated" href="mailto:JWLua@jwmusic.nu">JWLua@jwmusic.nu</a>
<a class="moz-txt-link-freetext" href="http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu">http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu</a>
</pre>
</blockquote>
<br>
</body>
</html>