<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link="#0563C1" vlink="#954F72" style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal>Problem solved. You will recall that after being processed by my JW Lua script, my files were blank in Scroll View (and sometimes, merely switching to Scroll View would crash Finale).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>I isolated the section of JW Lua code that was triggering the issue. About halfway through the script, there is code that deletes all of the original staves from the source document: they have already been copied onto newly appended staves and must now be discarded. But running that section of code, on its own and without anything else, caused Scroll View to be blank (Page View was fine).<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>The files I am working are very old (from about 20 years ago). I discovered that if I created a brand-new Finale file and ran my code on this new file, there was no problem with Scroll View.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Finally I found that if I open one of these ancient Finale files, and then run Document => Data Check => File Maintenance prior to running my JW Lua script, Scroll View is restored to normal operation.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>When I run File Maintenance, it doesn’t find much wrong with the files *<b>except</b>* that it always “removes” one staff that was “deleted” at some time in the past.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Another thing that is now fixed by File Maintenance is that the files, after being processed in JW Lua and exported to another app via XML, no longer have a blank “unknown MusicXML instrument” at the bottom of the score. This was not just a bore, but was sometimes causing instability in the destination app.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>So I’ve added File Maintenance to my routine, every time I open one of these old files for the first time. I tried to find a way to achieve the same thing programmatically in Lua but my various attempts to detect the “phantom staff” failed, and without being able to detect it, I cannot delete it.<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Martin<o:p></o:p></p><p class=MsoNormal><o:p> </o:p></p></div></body></html>