This documentation is based on the XE3 Build 20932 of 08-jul-2019.
•Q++Studio is compatible with the new QuarkXPress 2019, officially released on July 9, 2019.
•Expanded the help topic on DayValues inside the conditions of zap or conditional tokens.
•New versions of the worldwide public holidays apps for Android or iPhone and iPad. These 2 apps have been re-written from scratch, using the native development tools for each of the Android and iOS platforms, making for lightweight and lightning fast applications.
•Fixed a bug in the evaluation of zap and conditional tokens where the condition included a token with a specific DayValue (Blueline, 8-july-2019).
•Chris Hickey, the new Quark CEO, has announced that QuarkXPress 2019 would be released on July 9, 2019. As usual, Q++Studio will support this new version of QuarkXPress on the first day of its release (in fact, Q++Studio has been compatible, for weeks, with all the beta versions of QuarkXPress 2019).
•The browser-based online version of the documentation now uses a responsive skin making it adapt to all types of screens, including mobile phones. In addition, the online documentation's full-text search now uses server-based PHP, making for faster and more flexible searching.
•The updater now installs versions of the qpp xtension that work with both the original version of QuarkXPress 2018, and with the the later versions, beginning with the October 2018 Update 14.1.2 which used different ICU libraries, breaking any previous installations of QuarkXPress 2018. This should make the occurrence of message 182120 a thing of the past, regardless of the minor version of Quark 2018 that you are using.
•Q++Studio is compatible with the current beta version of the recently-announced QuarkXPress 2019. As usual, we expect to release a version of Q++Studio that is fully compatible with this new version of QuarkXPress, on the day it is officially released.
•Added a message to interrupt informatively the scanning or inspection of a Quark file, if the selected version of QuarkXPress is improperly setup, and the relevant error messages, such as messages 175665 or 175670 or 182120, for example, have not been addressed.
•Modifying saints exceptions individually would not apply any change (Blueline, 13-may-2019).
•The dates generated by the dates (variable) property of insert scriptlines would be based on the range of dates of the script's main grid, and not that of the parent scriptline of the insert (Brepols, 10-may-2019).
•Any box containing a BOXFIT token, and which does not have text overflow initially, will now be automatically reduced in size to 3 points, to ensure text overflow, before the actual BOXFIT processing begins. This will make your layouts that use BOXFIT more legible and avoid the error message 179375 (requires Quark 2016 or above).
•The bullet glyph used for bullet points in the webhelp online documentation are now larger and more visible.
•The generated output files are now saved, closed and re-opened, before performing the check for text overflow, to ensure that the generated file has been fully internally updated by QuarkXPress, and that no spurious text overflow messages appear.
•The individual pages of the script preview now display the label of PlaceHolders, and the file name of QuarkPages, centered and wrapped on multiple lines (instead of a single, potentially truncated, line as was the case before).
•Fixed the spurious occurrence of message 179730 which would occur if some formatting was to be applied to all tokens, regardless of their type, such as in setting some formatting for outside days in the monthly outside days section of Grid Options, but when the token is one of the image tokens whose text will be ignored as the textbox is changed to a picture box (JMata, 20-apr-2019) .
•Any very large single Xtags instruction (over 4096 bytes) could cause QuarkXPress to abort diary generation (Brunnen, 11-apr-2019).
•The error message displayed in the macro interruption dialog would, under certain circumstances, be stripped of its most important information, leaving a generic error message (Brepols, 5-apr-2019).
•If the result string of a holidays response token contained one or more tokens, which themselves contained a colon, such as specific holidays sets modifiers, then that colon would be mistaken as the beginning of a duration suffix (Zettler, 4-apr-2019).
•Over the past 4 months, all the chapters and topics of the help and documentation have been fully revised, with updated and expanded text, and all new screenshots, based on the latest version of Q++Studio running under Windows 10 (over 2200 topics and 1300 images).
•Added code to slow down the importation of large plain Quark files (files of over 20 pages), to allow any anti-virus to catch-up with the importation process, and the creation and deletion of temporary files (although this should not be necessary, if your anti-virus and firewall are setup as specified here).
•The find and change fields of the saras definition window now use a fixed font to make these 2 strings easier to read.
•Added a space after bullets point bullets in the help preview of the diary generation messages dialog.
•Added code to prevent trying to scan or generate if some files are missing from your QuarkXPress installation.
•Improved the layout of the log generated by the worldwide public holidays updater.
•The updater now pro-actively replaces missing DLL files in the QuarkXPress 2018 installation folder due to a problem in the 2018.21 upgrader (19-mar-2019).
•Added code to gracefully handle failed connections to the FTP server (19-mar-2019).
•Fixed a bug in the saving of the backup purging settings of the server settings, whereby the weekdays, and first/last of the month, settings would not be saved, and would always revert to their defaults (Lecas, 12-mar-2019).
•Fixed a few UI glitches of text controls not being aligned with each other, in particular in the holidays recurrence rules.
•The tooltip variable evaluation of the macro debugger would not find the correct variable under the mouse cursor, for long lines, and if you changed the size and font used to display macros (27-feb-2019).
•If a holiday used in a conflict rule was subsequently ignored, then the warning message 173490 would be properly triggered, but the interface of the holidays manager would not identify the conflict rule as being broken (26-feb-2019).
•The secondary indices of multiple index macro tokens, used in the text on left or text on right fields of multiple holidays options or moon phases display options, would not be identified and listed in the macros property editor (Lecas, 25-feb-2019)
•Calling the macro functions Assert and RaiseError with the parameter bAbortScript set to true would not abort the script; it would just keep logging the errors until the end of the script (12-feb-2019).
•Fixed a couple of UI glitches in the macros editor. When pressing F3 in the macros editor, an unfiltered list of functions would be displayed, instead of one limited to function of the right type, and the parameter list of void functions would be truncated (9-feb-2019).
•Fixed a rare bug which would occur when using the tab character insertion minicalendar modifier, with a split minicalendar whose first half did not have trailing empty positions (JMata, 7-feb-2019).
•Improved the usability of the specific dates property editor (drag and drop to add or remove a date and double-click on a date to add it to the list of fixed dates).
•The user interface of the slogan rules property editor has been fully re-designed.
•Added code to force QuarkXPress to always insert pages of non-facing pages output files on a new spread (Grieg, 30-jan-2019).
•Some dialogs would straddle 2 screens on dual-monitor systems (10-jan-2019).
•Fixed a dates array whose memory was nor being fully re-initialized each time a GridTemplate was being re-scanned, causing ghost dates to be used in insertion rules, in some extremely rare cases of removing dayvalue marker tokens from a template into which another template was being inserted, and which contained no tokens on any page other then the first (Nippecraft, 8-jan-2019).
•Fixed a small memory leak that would occur when changing the list of the exceptions of a recurring holiday (5-jan-2019).
See also: previous release notes.