User Tools

Site Tools


jwlua:fullscripts

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
jwlua:fullscripts [2013/09/24 18:08]
jariw
jwlua:fullscripts [2013/10/08 08:06] (current)
jariw
Line 1: Line 1:
 This page contains some longer scripts that are "​feature complete"​ in terms of their interaction with the Finale user. For shorter script examples, please refer to the page with [[jwlua:​quickscripts|quick scripts]]. This page contains some longer scripts that are "​feature complete"​ in terms of their interaction with the Finale user. For shorter script examples, please refer to the page with [[jwlua:​quickscripts|quick scripts]].
 +
 +The [[jwlua:​harpglisssample|Using JW Lua - Create Harp Gliss]] page also contains a full script that might be of interest.
  
 ==== Locked Systems Per Page ==== ==== Locked Systems Per Page ====
Line 91: Line 93:
 ==== Create Tacet ==== ==== Create Tacet ====
  
-This script creates a tacet for the selected region, regardless of if the section contains music or how the measures has been configured regarding multimeasure breaks. It requires that the Automatic Update for multimeasure rests is OFF for the file. Before the tacet , a user alert is displayed. The script also requires a selected region (JW Lua will automatically tell the user if a region isn't selected).+This script creates a tacet for the selected region, regardless of if the section contains music or how the measures has been configured regarding multimeasure breaks. It requires that the Automatic Update for multimeasure rests is OFF for the file. Before the tacet , a user alert is displayed. The script also requires a selected region (//JW Lua// will automatically tell the user if a region isn't selected).
  
 Specifying the multimeasure rest preference record 1 doesn'​t really matter here (any value would load the same preference data), but generally speaking for single-instance preference records, it's good practice to load preference record 1 anyway. Specifying the multimeasure rest preference record 1 doesn'​t really matter here (any value would load the same preference data), but generally speaking for single-instance preference records, it's good practice to load preference record 1 anyway.
jwlua/fullscripts.1380046102.txt.gz ยท Last modified: 2013/09/24 18:08 (external edit)