[JW Lua] ***SPAM*** Re: Undocumented finaleplugin fields and RGP Lua

[Robert Patterson]

Since (as I recall) JW Lua emits 9999 for the Finale Version for any
version of Finale after 2014, I elected to implement as follows:

Finale 2010 = 2010
Finale 2011 = 2011
Finale 2012 = 2012
Finale 2014 = 2014
Finale 25 = 10025
Finale 26 = 10026
etc.

This should allow any code that compares to 9999 to keep working the same.

MinFinaleRawVersion
MaxFinaleRawVersion

I'll add those to the list for 0.58.


On Mon, Dec 6, 2021 at 3:50 PM Jari Williamsson <
jari.williamsson at outlook.com> wrote:

> On 2021-12-02 21:45, Robert Patterson wrote:
> > MinFinaleVersion
> > MaxFinaleVersion
> >
> > I would like RGP Lua to recognize these as well, but only if they use
> > the raw Finale version. If they use the Finale year, I see little point.
> > (For 64-bit JW Lua, the version year seems to be always 9999.) Does
> > anyone know how these work? Is there a reason to continue supporting
> them?
>
> I see in the JW Lua sources that I never updated these beyond supporting
> 2014. So I guess noone uses them. :-) The idea was:
> Finale 2010 = 2010
> Finale 2011 = 2011
> Finale 2012 = 2012
> Finale 2014 = 2014
> Finale 25 = 2025
> Finale 26 = 2026
> etc.
>
> This was to assure that each subsequent version number should be higher,
> to span the logical gap between Finale 2014 and Finale 25.
>
> I also was thinking about raw version number checks (when MakeMusic
> started to implement new document features in the versions updates). I
> suggest that you use new fields for this, for example:
> MinFinaleVersionRaw
> MaxFinaleVersionRaw
>
>
> Best regards,
>
> Jari Williamsson
>
> _______________________________________________
> JWLua mailing list
> JWLua at jwmusic.nu
> http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jwmusic.nu/pipermail/jwlua_jwmusic.nu/attachments/20211206/a26fbfd7/attachment.html>