Options let you set common settings, as well as control specific settings. For more info on sections, see Insert a section break. To do this, choose Select Sections in the Restrict Editing panel. If you want to protect only parts of the document, separate the document into sections and only protect the sections you want. Open the form that you want to lock or protect.Īfter selecting restrictions, select Yes, Start Enforcing Protection. If you want to limit how much others can edit or format a form, use the Restrict Editing command:
Select the content control that you want to change. For example, the Date Picker control offers options for the format you want to use to display the date. Set or change properties for content controlsĮach content control has properties that you can set or change. Select the Legacy Form control or Active X Control that you want to include. Go to Developer > Legacy Forms drop-down. Using the Macmillan Tools macrosĭocumentation for using the Macmillan template (and styles more generally) is available here.Legacy form controls are for compatibility with older versions of Word and consist of legacy form and Active X controls.Ĭlick or tap where you want to insert a legacy control. You do not need to attach any additional binary files to the Release. Once merged with the master branch, open a new Release in GitHub using the same version number string as the tag. When a new version is ready for release, the latest_version should be updated in global_config.json (and any relevant region config files). The version number itself should be prefixed with a v followed immediately by the version number: v2.9.5 The current version number should be stored in the template's CustomDocumentProperties with the key Version. If the local config file also contains a files key, those values take precedence over the global and region config files. The user's region is stored in a local config file. This is where you should specify which release that region should be on. Users are prompted to select their region data in the region config files takes precedence over data in the global config.
If neither is present, the latest file on the master branch used. The values for the global_config.json file itself are also stored in the template's CustomDocumentProperties.įiles will be downloaded from the commit tagged with the value in the latest_release key, unless there is a branch key present in which case the file will be downloaded from the HEAD of that branch. The files key contains info for each file the template needs. Global_config.json contains data the template needs to manage file downloads and updates. The Macmillan template uses the excellent VBA-JSON and VBA-Dictionary projects. We haven't tested anything on Office 2016 yet, but we're working on it! Installationĭownload the Word-template.dotm file and double click the icon to open a new file. Mac: Tested and supported for 2011 only.PC: Tested and supported for 2007 - 2013.
When installed on a PC, the user gets a custom "Macmillan Tools" tab on the ribbon with buttons to launch the macros when installed on a Mac, the user gets a custom floating toolbar. The Macmillan Word template contains a variety of VBA macros for use in working with manuscripts.
0 kommentar(er)
