Loading...
We sent you this message because you have purchased one or more Just Great Software products (AceText, DeployMaster, EditPad, HelpScribble, PowerGREP, RegexBuddy, or RegexMagic), or because you have subscribed to the Just Great Software Newsletter. You can instantly remove yourself from our mailing list.
It's been a few months since we sent out our newsletter. We've been experimenting with a different way to bring you news and updates about our products.
All our products now have the ability to automatically check for new versions and other news. Each product automatically checks for news only once per day. At most one news item is shown each day for each product. If you haven't use the software in a while and there are multiple news items you haven't seen, you'll still only see one item per day. It automatically prioritizes updates for products that you use over updates for other products and over other news. You can also choose whether you want each product to show only updates for itself or also for other products that you use or for all our products.
Each product has a News and Updates item in the Help menu that checks for news whenever you select that menu item, allowing you to read news when it suits you rather than automatically when the product starts. This menu item too shows at most one news item at a time. It also tells you when there is no news. Either way the message will have a Settings button that allows you to configure what news you want to see. You can separately configure which news you want to see on request via this menu item and which news you want to see automatically. By default you will automatically see news and updates for any of our products that you've used in the past 30 days. The Help|News and Updates menu item shows news for all our products by default. News settings and history are automatically shared between all our products.
You can disable all news and updates, except for critical updates (catastrophic bug fixes) of which we hope to have very few, if any, ever. News is shown in a modeless window. If you don't want to read the news immediately, you can continue working with the software while the news window stays open. All in all, the automatic news system is designed to give you news and updates in a timely fashion without every bombarding you with lots of news or getting in your way.
We haven't decided yet whether this automatic news system will replace or complement our email newsletter, or what the frequency of the email newsletter will be. (But surely no more frequent than once per month.)
In the past, the web page at http://www.just-great-software.com/newsletter.html would show the latest issue our newsletter. Now it shows the latest update for each of our products from the system for automatic news and updates. It is updated as we write the articles instead of when we send out the email newsletter.
If you use an RSS reader, you can subscribe to our RSS feed at http://www.just-great- software.com/newsletter.xml which now shows the news we publish through the automatic news and updates system.
Each product still has its Check for New Version item in the Help menu. This opens a web page in your default web browser that tells you whether there is a newer version of the software you're using.
Below you'll find the most important fixes and improvements in our products since the last issue of our newsletter.
DeployMaster 6.1.1 is now available for download.
On the Project page, you can specify a readme file, a license agreement, and support DLLs. All these files are optional. Previously, DeployMaster ignored these file paths if they were invalid. Now, non-existent files on the Project page are treated as non-fatal errors. This way you don't accidentally build an installer with reduced functionality when a file goes missing. It's also consistent with how non-existent files are treated on the Files page.
DeployMaster 6.0.0 introduced the ability to build installers that install for the current user without administrator rights. To implement this, a second set of default installation folders was added on the Project page. Additional checks were added to the build process to ensure that the default installation folders are valid and appropriate for installations for all users or the current user. These new checks broke the ability to specify absolute paths for installations for all users. This has been fixed.
Using absolute paths is not recommended, however. If the path's drive does not exist and the user does not change the installation folder then the installation will fail. You can use the %SYSTEMDRIVE% placeholder instead of C: if you want to install onto the drive that Windows is installed on. There were no issues with this placeholder in DeployMaster 6.0.0 through 6.1.0.
You can only use absolute paths or %SYSTEMDRIVE% for default installation folders for the current user if you turn on "require admin rights" for current user installs. If the user does not have administrator rights they are likely not able to write to the root of the C: drive.
If for any reason your installer is not able to create a file or folder it shows an error message to the user that mentions this file or folder. If this file or folder had a percentage sign in its name then the error message would complain about the percentage sign instead of saying the file or folder could not be created. Percentage signs are allowed as literal characters in file and folder names. They only have a special meaning in DeployMaster when used as part of a placeholder at the start of a path.
On the 3rd Party page, you can now specify .NET 4.7 as the minimum required .NET version. The Windows 10 Anniversary update includes .NET 4.6.2 but it's a different build than the .NET 4.6.2 that you can download separately other versions of Windows. Your installer now correctly detects this as .NET 4.6.2 if you specify .NET 4.6.2 as the minimum required .NET version.
On the Media page you can use the placeholders %VERSION09% and %DATE09% in the file name for the generated setup to insert the applications's version number and release date stripped of all non-digits. These have been supported since DeployMaster 4.1.0. But they were broken in DeployMaster 5.0.0 through 6.0.1, stripping the digits instead of retaining only the digits.
RegexBuddy 4.8.0 is now available for download.
This release brings RegexBuddy up-to-date for all the applications that it supports. Newly supported versions are Boost 1.64, Delphi and C++Builder 10.2 Tokyo, PCRE 8.40, PCRE2 10.23, Perl 5.26, PHP 7.1.6, Python 3.6, R 3.4.0, Ruby 2.4, and std::regex in Visual C++ 2017.
Boost has its own ideas about how quantifiers on recursion should work and even changed its mind in version 1.60. RegexBuddy 4.7.0 could not emulate this so it treated all quantifiers other than `*` as errors when used on recursion with Boost. RegexBuddy 4.8.0 now correctly explains Boost's behavior on the Create page and correctly emulates it on the Test page. Though you could consider this behavior to be bugged if you're familiar with recursion in other flavors, it is the way how Boost works. So even in Helpful mode RegexBuddy no longer flags quantifiers on recursion as an error.
Previously, in free-spacing mode, RegexBuddy treated all spaces and line breaks, including Unicode spaces and line breaks, as free whitespace. This is what our own applications do. But they are actually unique in that aspect. RegexBuddy now knows that many flavors only treat the ASCII space and tab as free whitespace and that various line break characters other than the carriage return and line feed may or may not be free whitespace. Many regex flavors are inconsistent in which line breaks they recognize as free whitespace or as the end of a comment when compiling the regex and which line breaks they recognize when matching start and end of line anchors.
RegexBuddy is now better able to detect regexes with the potential for infinite recursion and endless recursion. Some flavors, like Ruby, flag this as a syntax error. RegexBuddy now does so too for those flavors. Some flavors crash upon infinite recursion. This too is now a syntax error in RegexBuddy. Previously it was only a matching error. In Helpful mode, RegexBuddy now flags unavoidable infinite recursion and endless recursion as a syntax error for all flavors as such regexes can never find any matches. RegexBuddy continues to allow potential infinite recursion for regexes that can find matches. When infinite recursion does occur with such regexes, that continues to be a matching error.
A regex syntax error is an error that occurs when the regular expression is parsed or compiled, before it is actually used. A matching error is an error that occurs while the regular expression is being applied to a subject string. In RegexBuddy, the Test panel indicates both types of errors. But the Create panel and syntax highlighting of the regex only indicate syntax errors. So by turning matching errors and crashes into syntax errors you can find them earlier.
RegexMagic 2.7.0 is now available for download.
This release brings RegexMagic up-to-date for all the applications that it supports. Newly supported versions are Boost 1.64, Delphi and C++Builder 10.2 Tokyo, PCRE 8.40, PCRE2 10.23, Perl 5.26, PHP 7.1.6, Python 3.6, R 3.4.0, Ruby 2.4, and std::regex in Visual C++ 2017.
When RegexMagic generates your regular expression it also lists all the matching options that the target application or programming language supports. Options that affect your regular expression are indicated as "required options". You have to set these in your application to get the same results as in RegexMagic. Options that do not affect your regex are indicated as "unused options". RegexMagic shows your application's defaults for these options for completeness. Many applications have an option to ignore whitespace. RegexMagic calls this "free-spacing" when on and "exact spacing" when off. Previously, RegexMagic always treated this as a required option. Now, RegexMagic knows that regular expressions that don't have spaces aren't affected by this option.
AceText 3.4.2 is now available for download.
Whenever you had AceText perform a search using a regular expression (regardless of whether you had it make replacements) and whenever you had AceText perform a search-and-replace across all clips (regardless of whether you used a regex), AceText would leak an amount of memory equal to the size of the clip being searched through. This meant that whenever you performed such searches, AceText's memory usage would increase and that memory would not be available for reuse by AceText or other applications until you closed and restarted AceText.
AceText is primarily designed to work with very small snippets of text. So under normal usage, the amount of memory leaked was small enough that it didn't cause any problems. That's also why it had gone unnoticed until now. But if you had AceText do a large search-and-replace, such as replacing many thousands of regex matches in a clip that contains a few million characters, AceText could quickly exhaust your computer's available memory. This would cause AceText to crash. It could also cause other applications to crash if they were starved for memory at the wrong time.
This bug has now been fixed. Any extra memory needed for searching is now immediately reused. Even a massive search-and-replace will only show a slight increase in memory usage. The undo history will use a small amount of memory to allow you to undo the search-and-replace. That memory is released when the collection is closed or the item falls off the undo history.
Replacing all matches in a single clip now adds only a single item to the undo history, just like replacing all matches in all clips already did. That one undo item undoes all replacements at once.
PowerGREP 5.1.2 is now available for download.
PowerGREP's installer can now install PowerGREP for the current user only without needing administrator privileges. To install PowerGREP this way, click the Advanced Installation button and then the Install for Current User button. This choice is only available the first time you install PowerGREP. If you want to change, you'll need to uninstall and reinstall.
If you click the Immediate Installation button then you'll automatically get a per-user installation if you run the installer from a Windows user account that cannot obtain administrator privileges, and PowerGREP was not previously installed for all users. If you have PowerGREP 5.0.x installed, that counts as an installation for all users.
Previous versions of PowerGREP already supported portable installations that don't require administrator privileges. These are still supported. The disadvantage of a portable install is that it won't create file associations or shortcut icons. The new per-user installs are full-featured installs with file associations and shortcut icons and everything. The installer for the free trial version also supports per-user installs (but not portable installs).
PowerGREP 5.0.0 and later support regular expression recursion and subroutines. Version 5.1.2 turns certain forms of recursion that could never find any matches into syntax errors. This way you don't waste time running a search with a regex that could never produce any results. Actions that are aborted because of a regular expression that exhibits catastrophic backtracking or infinite recursion now show a proper error message in the bottom half of the Results panel that explains what you need to do to fix your regular expression so the action can run.
On the Results panel, sorting matches alphanumerically now works correctly. Previously, alphanumeric order was only correct if you selected it on the Action panel. If you did not, selecting alphanumeric match order on the Results panel caused matches to be grouped and sorted incorrectly. Alphanumeric order is new since PowerGREP 5.0.0. Alphabetic order which PowerGREP has had since version 1.0.0 was not affected by this bug.
When an action overwrites files, backup copies are now created more reliably. Some backup options can use the same folder for backups of files that are in different folders. Setting "backup file destination type" to "single folder" is the most obvious way to create this situation. If your action ends up modifying multiple files with the same name then there can be a naming conflict when they are backed up into a single folder.
If you set "backup file naming style" to any of the "multi" options then PowerGREP now ensures that it always uses unique names for backups of files with the same name. Previously it could accidentally use the same name if it modifies multiple files with the same name at the same time.
If you set "backup file naming style" to one of the "single" options then the name of the backup is always the same. In this situation PowerGREP now refuses to modify the second and following files with any given name that need to be backed up. It adds an error explaining this to the results. Previously, PowerGREP would modify all the files. The backups of the second and following files with a given name would overwrite the backup of the previous files with the same name.
Backup file destination types that place backups in archives now create folder trees inside the archive when a folder is included with its subfolders and the target type is set to modify the original files or to place target files into a folder tree or archive. This makes backup file destination types that use archives consistent with target file destination types that use archives. It also makes them consistent with how the Assistant panel says they're supposed to work.
Backups are now created correctly when you mark a folder inside an archive and set "backup file destination type" to "folder tree". Previous versions of PowerGREP would fail to create backups and as a result would not overwrite any files in this situation.
Two bugs were fixed to ensure that the Results panel makes backups correctly. In PowerGREP 4, the Results panel used the backup option from the Editor Preferences. But in PowerGREP 5 the Results panel uses the backup option you had on the Action panel when you previewed or executed the search-and-replace. This ensures backups are made in the same way whether you make replacements using the Replace button on the Action panel versus using the Preview button on the Action panel and then using the Make All Replacements button on the Results panel. But this change introduced a couple of bugs. PowerGREP 5.0.0 though 5.1.0 did not make backups when making or reverting replacements on the Results panel if "no backups" was selected in the Editor Preferences. They would fail to make or revert replacements if "no backups" is selected on the Action panel and another backup option is selected in the Editor Preferences. These two bugs have been fixed. Now, the Results panel correctly uses the backup settings you had on the Action panel at the time the results were produced, regardless of what you specified in the Editor Preferences.
PowerGREP 5.0.0 made it possible to directly search through the contents of the clipboard by adding the clipboard as a node to the File Selector. PowerGREP 5.1.0 expands on this by allowing you to import file listings from the clipboard. If you click the Import button on the File Selector panel then you will see a new Paste button on the Import File Listings dialog box. This adds a reference to the clipboard as a "file" to import file listings from.
In the External Editors section in the Preferences you can now select whether an editor should be available to open files, folders, and/or archives. This allows you to easily open folders and archives in external file managers. The Explore Folder command in the File Selector's context menu now uses your computer's default file manager instead of always using Windows Explorer.
PowerGREP's converter for XLS and XLSX files is now significantly faster on spreadsheets that contain large numbers of blank cells. Currency values in XLS files now correctly show the currency symbol.
PowerGREP now supports the RAR 5.0 archive format. If you enable "RAR archives" in the archive format configuration then PowerGREP automatically checks whether each .rar file uses the old or the new RAR format.
PowerGREP can now search through disk images using the NTFS (Windows), HFS+ (OS X), ext2, ext3, and ext4 (Linux) file systems. You can enable or disable these as part of the archive format configuration. If you upgrade from PowerGREP 5.0.x to 5.1.0 then these new formats are automatically added to the predefined archive format configurations. If you load an action or file selection saved with a previous version of PowerGREP, then the new formats are not automatically added. This ensures that a saved action or file selection continues to work exactly the way it did when you saved it. If the saved file selection uses a archive format configuration as predefined in 5.0.x then this is indicated with a number such as (2) in the File Selector to indicate that it uses different settings from the new predefined configuration in 5.1.0.
On the Sequence panel, adding, deleting, and reordering steps now preserves file selection references between steps. If a step has its own file selection, the list of steps now shows a summary of that file selection instead of the text "own file selection". That makes it easier to distinguish those steps if your sequence has multiple steps with their own file selections. If a step references the file selection of another step that is set to use the File Selector, then both steps now correctly use the File Selector. Previously the step with the reference would not search through any files at all. The Comments box now wraps long lines just like the Comments boxes on the Action and Library panels already did.
EditPad Lite 7.6.1 is now available for download.
Windows 10 changes the way the mouse wheel works in Windows. In older versions of Windows, the wheel scrolled the window that had keyboard focus, regardless of the position of the mouse pointer. In Windows 10, the wheel scrolls the window under the mouse pointer. EditPad now correctly implements the Windows 10 mouse wheel behavior when running on Windows 10. The mouse wheel behavior in EditPad is unchanged when running on an older version of Windows.
It is possible for a regular expression to match half of a CRLF pair. The regexes \r and \n are the simplest examples. But EditPad does not allow a search match to begin or end in the middle of a CRLF pair because its editor control treats all line breaks as indivisible. So when a regular expression matches half of a CRLF pair, EditPad extends the search match to include the whole CRLF pair so that searching selects the whole line break and making replacements replaces the whole line break. If you need to delete half of a CRLF pair to change the line break style, you can use the dedicated line break conversion commands in the Convert menu. None of this is new. What is new is that when you turn on Options|Visualize Line Breaks then the Search|Highlight command now correctly highlights entire CRLF pairs.
With the Previous Editing Position and Next Editing Position commands in the Go menu you can go backward and forward through the places in the active file that you've recently made changes. This allows you to quickly jump back and forth when you're editing a file in several different places. When using these commands in previous EditPad 7.x.x releases when part of the file was selected that selection would persist even when the option for persistent selections was turned off in the Editor Preferences. This could cause you to accidentally delete the selected text when typing or pasting text after moving to a previous editing position. Now these commands remove the selection when selections are not persistent, just like moving the cursor with the arrow keys or the mouse removes the selection.
EditPad Pro 7.6.1 is now available for download. It includes the improvements made in EditPad Lite 7.6.1 as explained above.
If you open a file using the FTP panel and then use the normal File|Save menu item or corresponding toolbar button then EditPad Pro automatically uploads the file back to FTP if you are still connected to the FTP server. Otherwise it prompts to reconnect. In previous versions this was broken if the FTP login (user name) contained an @ sign. You could open and edit the file, but clicking the Save button would pop up the FTP connection dialog even if you were still connected to the server. Now, clicking the Save button will automatically upload the file even when the login contains special characters.
EditPad Pro now supports TLS 1.1 and TLS 1.2 in addition to TLS 1.0 and SSL 3.0 when connecting to FTP servers that use TLS encryption, when sending email through SMTP servers that use TLS encryption and when accessing HTTPS URLs that you added to the Tools menu with the option to capture standard output. EditPad Pro automatically negotiates the highest version of TLS that is supported by both EditPad Pro and the server you're trying to connect to. EditPad Pro now includes version 1.0.2k of the OpenSSL DLLs. You can replace these DLLs with a different version or even delete them if you don't need TLS and SSL support.
In Options|Configure File Types|Navigation, you can tell EditPad Pro to add automatic folding points based on the indentation of the text. By default, EditPad uses this option only for Python scripts. In Python, indentation determines the structure of the code (whereas in other languages it is simply a visual aid for the programmer). But you can turn this on for any file type for which you want to be able to easily fold away indented lines. Previous versions of EditPad did not always correctly add automatic folding points based on indentation. This bug has been fixed.
The *Convert|\uFFFF -> Characters* menu item replaces Unicode escapes in the form of \uFFFF with the actual Unicode code point. In previous releases this command had a fundamental bug that caused it to misinterpret files or selections containing backslashes or letters u that weren't part of a Unicode escape. This has been fixed so the conversion now works correctly on all files. You may need to use Convert|Text Encoding to change the file's encoding to Unicode before using Convert|\uFFFF -> Characters so that all the converted code points can be represented in the file.HelpScribble 8.1.0 is now available for download.
HelpScribble's HelpContext property editor now supports Delphi 10.2 Tokyo and C++Builder 10.2 Tokyo. HelpScribble's installer will automatically install it if it detects that you have Delphi 10.2 Tokyo or C++Builder 10.2 Tokyo installed. HelpScribble's HelpContext property editor can assign HelpContext properties to controls in VCL applications and Multi-Device applications.
HelpScribble's installer can now install HelpScribble for the current user only without needing administrator privileges. To install HelpScribble this way, click the Advanced Installation button and then the Install for Current User button. This choice is only available the first time you install HelpScribble. If you want to change, you'll need to uninstall and reinstall.
If you click the Immediate Installation button then you'll automatically get a per-user installation if you run the installer from a Windows user account that cannot obtain administrator privileges, and HelpScribble was not previously installed for all users. If you have HelpScribble 8.0.0 or an older version installed then that counts as an installation for all users.
That's it for this month. Thank you for using our software, and see you next month!
Kind regards,
Jan Goyvaerts.
P.S.: If you know somebody who might be interested in any of the information presented in this newsletter, feel free to use your email software's "forward" function to send them a copy.
This message was sent to newsletter@newslettercollector.com
You can instantly remove yourself from our mailing list.
Loading...
Loading...
