6.1.1 6.1.2 6.1.3 6.1.4 6.1.5 6.1.6 6.1.7 6.1.8 6.1.9 6.1.10

Helix RADE Classic 6.1 is a feature release, primarily focused on Design Mode changes that complement the macOS products and enable additional functionality in Client/Server. Helix RADE 6.1 is still a Classic-only application, but the new features and changes make working on collections (whether for use with the macOS native Helix products or not) a more productive experience. There are a few new features, some specification changes, and a number of bug fixes.

Helix RADE Classic 6.1 is not a free update for owners of previous Helix products. Older Helix serial number and key combinations do not work with this release. Visit our web store or contact QSA ToolWorks for information on purchasing the Helix RADE Classic 6.1 upgrade.

Helix RADE Classic 6.1 is a general release and can be used with all existing collections. We encourage all customers to update existing collections to Helix RADE Classic 6.1, regardless of whether or not they are experiencing problems in the areas that are specifically addressed by this release.

Helix RADE 6.1 represents an interim step in our work in updating our code for macOS. Helix Server, Helix Utility and Update Collection are currently macOS native. macOS native versions of Helix Client & Engine are expected in the coming weeks.

Helix RADE Classic 6.1.6 is a bug fix release. Helix RADE 6.1.6 is still a Classic application, but the bug fixes make working on collections (whether for use with the macOS native Helix products or not) a more productive experience.

Helix RADE Classic 6.1.6 is a free update for owners of Helix RADE 6.1.x licenses. Simply download the new version and use your existing emablement keys to activate it.

For owners of Helix RADE 6.0.1 or earlier, this is a paid upgrade. Existing Helix 6.0 keys do not work with this release. Log in to your account or contact us for information on purchasing this upgrade.

Helix RADE 6.1.4: Mac OS 9.1 and higher
(Or in Classic mode on PowerPC based Macs running macOS 10.1 through 10.4.x.)

Introduction

Built on Helix’s copy/paste structure feature, the Helix Clippings menu allows you to easily create structural elements for reuse in your collections. Users, Sequences, Relations, and the various icons within Relations can be stored in Clippings for application at any time.

Helix Clippings are stored in a folder on your computer in the standard macOS clippings file format. They can be accessed via the Finder, and the Finder’s Preview function can give you a glimpse inside the clipping. Clippings made in View by Icon mode preview as a picture of the icons. Clippings made in View by Name or View by Kind mode preview as text (the names of the icons).

Clippings files can be copied like any other Macintosh file, moved from computer to computer, emailed, etc. However, they do contain a Macintosh resource fork, so care should be taken to avoid situations (FTP, FAT16/32 volumes, etc.) where the resource fork is stripped away.

Helix RADE Classic 6.1 includes a starter library of free Helix Clippings, and more are available on our web site. We also plan on using the Helix Clippings format to deliver more complex collection solutions, to be sold as commercial products. Both the free and commercial libraries are open for contributions from independent Helix designers. Contact us if you would like to submit Helix Clippings solutions.

Setup

To activate the Clippings menu, a folder (or alias to a folder) named Clippings must be found in the same folder as Helix RADE 6.1. If you installed Helix RADE 6.1 from our installer, a Clippings folder is created automatically and placed in the folder with Helix RADE. However, we recommend that you move this folder to another location and use an alias to it, so that you do not inadvertently lose your Clippings when upgrading to a newer version of Helix RADE.

If you want to configure your Mac the way Helix RADE macOS will expect it, navigate to your user’s ~/Library/Application Support folder and create a Helix folder in there. (If you have Helix Maintenance Manager installed, this folder already exists.) In the Helix folder, create a RADE folder and put your Clippings folder in there. Create an alias to that folder and put the alias in the folder with Helix RADE 6.1. Make sure the alias is named Clippings.

If the Clippings folder is found when a collection is opened with Helix RADE, the new Clippings menu appears in the menu bar as a © symbol, immediately to the right of the Window menu. If the Clippings menu does not appear, make sure you have a collection open. If it still does not appear, quit Helix RADE, navigate to the folder where RADE is stored, and make sure the folder (or alias) is named exactly. One common error is to have a trailing space after the name. It looks right, but Helix RADE does not see it.

Usage

The Clippings menu (shown at right) has three fixed commands, a divider, and the available Clippings files…

Save Selection As Clipping

Save Selection As Clipping creates a Clipping containing the structure of the selected icons. One or more icons must be selected, or this command is disabled. When the command is chosen, a dialog box appears giving you an opportunity to name the Clipping and to save it in any place you choose.

Because this is a feature designed for macOS, the Classic dialog box leaves much to be desired. The first time you use this command you must navigate to the Clippings folder, or the file will be saved in the default location as determined by your Classic OS. This is typically your Documents folder, so you may want to place an alias to the Clippings folder in that location to make navigation easier.

Classic also suffers in that it does not know to hide the macOS file extension. You can remove the file extension if you wish: Helix understands that these are Clippings either way.

Save Selection as Clipping uses the Classic clipboard to create Helix Clippings, so data on the clipboard will be replaced when a Clipping is created.

Show Clippings Folder

Show Clippings Folder opens a window in the Finder and reveals the actual Clippings folder. This is useful if you want to copy your Clippings to another location, rearrange the contents of the menu, or add new items to the folder

Refresh Clippings Menu

Refresh Clippings Menu updates the contents of the menu by walking through the contents of the Clippings folder (as seen in the Finder). This is useful if you have added new items to the folder (or rearranged the contents) and need to force Helix to see those changes.

Divider

The divider separates the fixed commands (described above) from the actual Clippings data below.

Clippings Data

Below the divider is the Clippings data. Anything placed in the Clippings folder is seen here. The Clippings menu supports hierarchical menus up to 5 levels deep, so you can organize your Clippings into logical projects.

When you select an item from the Clippings menu, that item is examined to determine if it contains Helix structural elements. If it does, the Paste Structure dialog opens allowing you to connect the structure found in the Clipping to the existing collection structure. The standard rules for pasting structural elements apply.

You can also place other files in the Clippings menu. If the menu item does not appear to contain Helix structure, Helix RADE hands it off to the Finder with an Open command. Text files will open with a text editor, applications will launch, generic clippings will open as clippings, etc. One powerful technique is to place AppleScript (or other) applications in the Clippings menu. The included “Quit, I’m Done” AppleScript demonstrates this capability by running as an applet that closes all the open windows, saves the collection, and quits Helix RADE.

Additional Notes:

• Be sure to close all unnecessary windows before applying Helix Clippings. You can not update any structure related to open icons. If the structure you are pasting references an icon in some other relation (e.g. via a lookup tile) and that relation window is open, the link can not be made and an incomplete icon is created.
• You can use CMD-1 (Next) to quickly cycle through the icons contained in the Clipping file. For icons that are intended as updates of existing structure, choosing the icon from the 4th column establishes the link. For new icons CMD-2 triggers the New button.
• It is not necessary to explicitly create new icons. Simply clicking the OK button creates new icons for any that have not been explicitly linked to existing icons.
• The contents of the Clipping file are compared to any pre-selected icons on a type by type and name by name basis. If the Clipping contains an icon of the same type and name as a pre-selected icon, Helix assumes you want to replace the old copy with the copy in the clipping.
• When first working with Clippings, it is a good idea to open (press CMD-O) the created structure immediately after applying the Clipping to make sure that all of the icons are referenced as expected.
• When pasting structure, it is possible to create structural anomalies that may be reported as damage by Update Collection or result in crashes when using Helix. One obvious example is a template used in a subform: replacing a template with a version that is larger than the original can create overlapping icons that Helix considers illegal. Should you apply a Clipping that results in a crash or a broken collection, please do not throw the collection away: contact us immediately so we can help you recover from the damage without losing your work. This is almost always possible in these cases. We are also interested in seeing specific examples of structure that cause damage when applied.

See Also

• New Features: Paste Structure: Rename Replaced Icons
• Spec Changes: Paste Structure Dialog Access
• Bug Fixes: Structure Paste Fails To Identify Top Level Icons
• Bug Fixes: Structure Copy/Paste Crashes
• Known Problems: Clippings Menu Disabled After User Mode Switch
• Known Problems: Clippings Menu Item Names

In prior versions of Helix pasting structure does not update the names of icons that are replaced with updated structure. This could cause confusion if you replaced, for example, the template TaxForm 2007 with TaxForm 2008, as the contents of the template would be updated, but the name would remain TaxForm 2007.

Helix 6.1 adds a Rename Replaced Icons checkbox to the Paste Structure Dialog. When this box is checked (it is by default) icons whose structure is replaced by updated code also have their names updated, using the name taken from the pasted structure.

Deselecting this box preserves the existing icon names, just as in prior versions of Helix.

The Rename Replaced Icons checkbox’s keyboard shortcut is CMD-R.

Icon names are not updated when bypassing the Paste Structure dialog: since Helix has no way of making a match between icons with different names, icons with names that do not match existing icons are always created as new icons unless you use the Paste Structure dialog to link them to existing icons.

Notify On Change is a new feature that allows you to set an attribute for each view that makes it update the Why? message (and therefore to beep) when a change is made to the content of that view. Anytime the view is redrawn to update data, the Why? message will be updated with a message that the data on a view has changed. The name of the view is also displayed.

Notify On Change is activated in the same manner as other view specific attributes (such as Shade Defaults or Keep Current: with the view open, select Notify On Change from the √ menu. The command displays a √ next to it when a view has this attribute set.

Notify On Change does not function in Helix RADE Classic 6.1 itself. This feature is part of Helix Engine 6.1 & Helix Client 6.1, which are macOS native applications. Helix RADE Classic 6.1 is used to enable this feature for views used in Helix Engine & Helix Client.

A few small improvements were made to make navigating in Design Mode a bit more efficient:

1. When working in a collection or relation window in list mode, you can now use CMD-down arrow to open a highlighted icon.
2. When working in an abacus, you can use the left/right arrow keys to switch from the tile list to the field (left) and abacus (right) lists. (These arrow keys do not yet work to switch from the abacus or field lists to another list.)

In addition to the original Command key commands, you can now add Shift-Command, Option-Command, and Shift-Option-Command modifiers to user menus.

These modified command keys are added in the user editor by holding down the modifier keys while dragging the key to the user menu, the same way standard modifier keys are assigned.

However, the Classic User Editor doesn’t quite know how to support these. As soon as you drag out a standard command key the keyboard representation of that key dims, making it impossible to assign commands using that primary key to other menu items. To work around this:

1. Remove the primary Command-key assignment (if necessary) so that the keyboard icon for that key is enabled.
2. While holding down the Shift, Option, or Shift-Option modifier keys, drag the key icon to the menu item it is to be assigned to.
3. When you release the key icon on the menu item, the modifier-enhanced version of the key command is drawn.
4. When you are done assigning key commands with additional modifiers, drag the un-modified key back to the desired menu item.

The ability to assign modified Command keys is actually a Helix RADE for macOS feature. We are making this feature available in its semi-complete form so you can take advantage of it in the macOS native versions of Helix Engine & Helix Client.

Additional Notes:

• Because the Classic User editor does not know when an extended modifier key command has been used, it is possible to assign the same extended modifier key command to multiple commands. There is no guarantee as to which command will be executed if you do this.
• Certain modified Command keys do not work as expected in Classic Helix programs. (Command-Option key combinations are the most often affected.) Be sure to test your shortcuts in User Mode before deploying them.

Unlike Helix 6.0.1 and earlier, Helix 6.1 does not rely on compiled forms. This is a significant ‘under the hood’ change, but we have handled it in a way that allows you to switch back and forth seamlessly between Helix 6.0 & 6.1. Compiled forms were eliminated because they provide no performance gain on modern (PowerPC G3 or later) hardware.

Consequently, the Compile Forms command is no longer found on the Design Mode menu.

In Helix 6.0.1 and earlier, the Paste Structure Dialog was not presented unless the designer held down the Option key while pasting structure. In Helix 6.1, the dialog is presented by default. To bypass the Paste Structure dialog, hold down both the Shift and Option keys while pasting.

For those who use the keyboard shortcuts: both Command-V & Command-Option-V now bring up the Paste Structure Dialog. Command-Shift-Option-V bypasses it.

The default font for label & data rectangles has changed from Geneva 12 point to Geneva 9 point. This was done to make ‘default’ code look better in collections used with macOS native Helix products.

Helix font defaults can be changed by editing the HFAC resources. If you are not familiar with resource editing, contact technical support for assistance.

This change has no effect on existing structure. Only new structure is affected.

A few changes were made to the default entry (aka: Quick Entry) templates:

1. The macOS style of indicating focus creates visual anomalies when rectangles are butted up against, or overlap, one another. Helix RADE has been modified to put a 4-pixel vertical gap between each field when creating a Quick Template. A 4-pixel horizontal gap is also created between the label and data rectangles.
2. The macOS style for data entry rectangles has a subtle 3D effect that takes some of the available space away from the text within. To compensate for this, the default font size for Quick Entry templates is now 9 point.
3. The width of label rectangles has been reduced slightly, and the width of data rectangles increased.

Quick Templates are created:

• When a designer fills a new template via the Quick Entry command
• When a designer creates a new entry view and with no template specified and chooses Clear Form, Find First or Find Last.

This change has no effect on existing structure. Only new templates are affected.

Two changes were made to the default list (aka: Quick List) templates:

1. The width of rectangles created in default list (aka: Quick List) templates is slightly smaller.
2. The default font size for Quick Entry templates is now 9 point.

This change has no effect on existing structure. Only new templates are affected.

The following Design Mode command keys have changed to avoid conflicts or to be more consistent with macOS:

• Quick Entry: Shift-Command-E
• Quick List: Shift-Command-L
• Quick Query: Shift-Command-G
• Open Query: Shift-Command-H
• Show Setup: Shift-Command-I
• Show Posting: Shift-Command-J
• Close Collection: Shift-Command-Q (Command also moved to just above the Quit command.)
• Preferences: Command-,

The following commands are now available in Design Mode:

• Sort Order…
• Refresh

When creating a new user, the following default command keys have changed to avoid conflicts or to be more consistent with macOS:

• Quick Query: Shift-Command-G
• Open Query: Shift-Command-H
• Preferences: Command-,

When creating a new user, the following default command keys have been added:

• Page Setup: Shift-Command-P
• Close Collection/Leave: Shift-Command-Q
• Close All: Command-Option-W

When creating a new user, the default position for the following command has moved:

• Autosave…: from the Set menu to the File menu, with the other Save related commands.

When creating a new user, the following commands are no longer part of the default set:

• Custom Paper…
• Export Ordered…

When creating a new user, the following commands are now part of the default set:

• Sort Order…
• Refresh

Commands & Command Keys can be added, removed, rearranged, etc. in the User Editor.

A query restricted view could fail to find the correct records if the view contains a post that modifies a value that is used to calculate the query. This has been fixed.

When duplicating a command rectangle with the Button Name option set to Use Abacus Output, the referenced abacus is not copied to the new rectangle, but the Use Abacus Output flag is not reset to use the typed-in name. The result in older versions of Helix is a button with no label, unless you had also supplied a static label, in which case the static label is used.

Helix RADE 6.1 and later properly reset the Button Name option and avoid the confusion. The duplicated rectangle is labeled using the name of the sequence until another name is designated by the collection designer.

Helix may crash when attempting to paste a view if the view contains both posting and subforms.

Helix crashes when attempting to copy/paste large amounts of structure.

Both of these bugs are addressed in RADE 6.1, however, it is still possible to crash Helix by copying or pasting very large structures.

A long standing bug in the Paste Structure dialog has been fixed. In previous versions of Helix, clicking the Next button bypasses sequence and user icons. In addition, if a sequence or user icon is part of the structure to be pasted, the Next button eventually selects ‘nothing’ (even though the status message indicates that there are still unlinked icons) and loses the ability to select other icons.

In rare situations, posting mysteriously stops working after a view is in use for a while. When this bug strikes, the post stops working and does not work again until remedial action is taken.

This bug is extremely rare and only seems to affect relations where there are a large number of post icons. The bug actually affects the internal posting package that is created when you select various post icons in the view’s four posting action columns.

This bug has been fixed by doing away with these packages altogether in Helix 6.1. The performance gain on modern hardware was negligible, and the added complexity was allowing subtle bugs like this to occur.

An obscure bug in the Classic Helix User Editor has been fixed. Helix keeps an internal table of user permissions for each view where a permission has been turned off. In a very specific situation, editing the menu of a User who did not have a particular view restricted in any way can result in that User inheriting restrictions for that view from the User doing the editing. This has been fixed in RADE 6.1.

Earlier versions of Helix RADE crash when trying to open a collection or relation window if all of the following conditions are true:

• One and only one icon is selected
• That icon is locked
• The collection (or relation) window is in List Mode (View by Name or View by Kind)
• The window was last used in Edit Mode (The toggle button at the top of the list has an A in it.)

Earlier versions of RADE also crash if you select a locked icon and then click on the Edit/Fast Find button to toggle modes.

Both of these bugs are fixed in RADE 6.1.

Pressing a command key to execute a menu item should always highlight that menu briefly to provide feedback to the user. In Helix 4.5.3 this function was disabled in the case of the Enter command. The rationale was that when Enter is called repeatedly in a sequence, highlighting the menu is a distraction and reduces performance.

In Helix 6.1, pressing the Enter key properly highlights the menu when an Enter command is executed. When the Enter command is executed as part of a sequence, the menu is not highlighted.

When an error occurs during the running of a sequence, there can sometimes be two error messages generated. For example, if a sequence attempts to enter a record that can not be entered because a validate check fails, there are two errors involved: the error because of the validation failure and the error because the record can not be entered.

Prior versions of Helix concatenated these two errors into a single entity, sometimes producing messages that did not make sense as presented. Helix 6.1 splits these messages onto separate lines, making it more apparent that two errors are involved.

Prior versions of Helix were not displaying the build number in the splash screen, making it difficult to determine precisely which version of Helix was in use. The build number is now shown when RADE launches and when selecting About Helix RADE from the Apple menu.

The Clippings menu should always be enabled in Design Mode. However, if an active collection or relation window has icons selected at the time RADE is switched to User Mode, when switching back to Design Mode the Clippings menu becomes disabled from that point on unless at least one icon is selected in the active collection/relation window.

When this bug strikes, you can still access the Clippings menu by simply selecting an icon in the active collection/relation window. You can also restore the correct behavior by deselecting all icons, switching to User Mode, and back to Design Mode.

To avoid this bug, be sure to deselect all icons before switching to User Mode.

Because Classic file names are limited to 31 characters and because the macOS extension for a Clipping is .pictClipping or .textClipping, files that are given long names in the Finder will appear in a shortened form with what may appear to be random characters at the end. This is normal and should cause no concern. The clippings will function as intended. This problem will disappear when macOS RADE is released.

Another problem with menu item names is that occasionally an item name in the Clippings menu will be replaced by the word Bumper. This is a harmless bug that can usually be resolved by selecting the Refresh Clippings Menu command and then waiting 5–10 seconds before doing anything else. This problem will be addressed in macOS RADE.

When a fixed point abacus is used as a source value in a post, either in the destination tile or a posting triplet, that same abacus is used to specify the On Condition value of an optional (i.e: conditional) sequence, and that abacus is not present on the template, the conditional sequence runs 100 times as often as specified.

Throwing away a field that was previously used in an abacus that is currently used by a query can result in Update Collection reporting that the collection is damaged. (Diagnostic Code: 36/xxxx/xxxxxxxx)

The damage caused by this issue is trivial and can be fixed simply by opening the query that contains the reference and making a change to the query specification. (In the case of a Permanent Power Query item, you have to go into the Permanent tab and deselect/reselect the items.)

In testing keywords in macOS, a major gotcha was discovered: the HKWT resource that defines the Keyword Separator Table is stored on the Helix application, not the collection. This means the if you modify your Keyword Separator Table, you must remember to update it with every new version of Helix you install.

Each collection can now have a customized Keyword Separator Table. Helix RADE 6.1.1 checks for the HKWT resource inside the collection. If an HKWT resource is found in the collection, that one is used instead of the default HKWT in the application.

More information on this change, along with a utility for managing HKWT resources, is found in this technote.

When pasting structure in View by Kind or View by Name mode, a 0305 error (and subsequent crash) could occur if Rename Replaced Icons was checked and the resultant renaming caused icons to move to a new location in the list. This bug is fixed.

In RADE & Engine 6.1: If a sequence encountered an error that prevented record entry, the Why? Message could contain garbage characters where the actual problem should have been reported. The same Enter command outside a sequence would properly report the specific error. From within a sequence only the generic ‘The record could not be entered.’ error was shown.

This bug is fixed: Helix now properly reports both the generic (sequence level) error and the specific (view level) error.

When working in a collection or relation window, holding the Option key down while choosing Select All now selects only unused icons. Adding the Shift key excludes indexes from the selection. (Indexes are often ‘unused’ but still required for optimal performance.)

The Command key equivalents (CMD-OPT-A & CMD-OPT-SHIFT-A) are also supported.

When rapidly selecting icons in Design Mode via shift-click, Helix no longer misinterprets an accidental double-click as a request to open all of the selected icons. Shift-clicking an icon now deselects it if it is already selected.

To open a group of selected icons, release the Shift key, then double click on any selected icon.

When opening a collection in Design Mode (or when switching to Design Mode from User Mode) holding the Option key down stops Helix from opening all windows except the main collection window.

The performance of the Design Mode zoom effect when icons are rejected is improved in two ways:

• The number of steps in the animation is reduced from 8 to 3. The animation is now much faster.
• When multiple icons are zooming back to their original positions, the animation now stops after the third icon. By then the user has typically gotten the message and the extended animation was deemed both time-consuming and annoying.

A rare combination of factors would result in the corruption of an index, resulting in records appearing twice in lists, or deleted records appearing as a blank line in lists. This has been fixed.

Helix Utility is also able to detect this problem and schedule the index for rebuilding, but lists could display inaccurate data between Helix Utility runs.

See this technote for details on the factors that triggered this bug.

Pictures over 64K, pasted into Picture fields, were not being recovered when the log file was applied after a crash. Upon recovery, the records containing the pictures were recreated, but the picture field was empty.

This is now fixed. All data types and sizes are properly recovered from the log file after a crash.

If a field icon is currently used in a quick query, Get Info on that field would not report that it was used by the view. The field could not be thrown away (because it was in use) but Get Info would not reveal where it was used. This has been fixed. Get Info now shows the view in the list of references.

In addition, when such a view is opened by double clicking in the Get Info reference list, a Why? message is set informing that the field is used in the Quick Query.

Icons that are not referenced by other icons (and may therefore be thrown away) are indicated by text marker [-] at the beginning of the Contents column (in View by Name and View by Kind modes). Fields that are designated as Keyword fields or had simple validations attached were not showing the [-] marker even though they could be discarded. Now they do.

It was discovered that every four billionth attempt to write lock a record would fail, and the record could potentially be edited by two users simultaneously. A user would have to write lock a record once every second of every day for 136 years to reach this number, so we are confident this bug has never affected any Helix user to date. Nonetheless, it is now fixed and will not affect users no matter how many centuries their databases are kept in use.

During export operations (both regular and Apple event) the internal field counter was set too high. This would occasionally cause a crash in Helix, depending on the contents of memory just beyond the true last field. This bug has existed since at least Helix Express 4.0 (and probably since Helix 1.0) and although we never had a crash report in Classic Helix directly attributable to this bug, it was a theoretical possibility. Therefore the fix was also applied to Classic Helix.

The items available in the ‘mini menu‘ — the one that appears when you launch Helix RADE or Helix Client but do not open a collection — contained a number of pointless commands that were always disabled. Those have been removed.

A new option has been added to the Clean Up command, enabling it to gather all icons together in the visible part of the workspace. See the release notes for details.

The Static Enter command can now be placed on User Mode menus.

1. A 'lost feature' in the User menu editor was found and revived: Helix has always supported pressing Command-Tab to create a new empty menu bar item. But since the Command-Tab key command is used to switch applications in OS 9 and later, that key command is not passed through to Helix. The key command is now Command-Enter or Command-Return.
2. The starter slot that is shown when creating a new menu in the User menu editor has been enlarged.

When opening a collection, you can now go directly to Design Mode (bypassing User Mode) by holding down the Option key.

The Show Clipboard command now has a Design Mode command key equivalent: CMD-K.

A longstanding bug was discovered in Helix that could result in database corruption when editing a label rectangle containing a picture over 32K by double clicking the rectangle to access the settings dialog.

Fixing the actual bug would take more time than we want to devote to Classic Helix now, so to avoid the bug, Helix now displays a dialog intructing you to use menu items to make the desired attribute changes. (You can also cut the picture from the rectangle, open the dialog, make the desired changed, close the dialog, and repaste the picture, if preferred.)

A bug that caused Helix RADE to fail to show all of the records in a report (list) when there were more than 32,766 records in the report is fixed.

A rare combination of circumstances, an indexed field with a default value on a cold form using Option 1 posting to change the field value from undefined to the default value, resulted in corruption to the index built on that field. This bug is fixed.

A bug that caused conditional sequences to run 100 times the expected value when a fixed point value is used as the trigger count and that same value is posted to another relation and that same value is displayed on the view has been fixed.

When the keyword separator table was updated, the German eszett character was inadvertently left out of the word character list.

Helix customers who use the eszett character in text stored in keyword fields need to rebuild all keyword indexes or keyword search results will be inaccurate.

More information on keywords, along with a utility for managing HKWT resources, is found in this technote.

The Keyword Index progress dialog would sometimes fail to show the name of the keyword field for which the index was being built. This was fixed in Helix Server macOS 6.0, but the fix had never been applied to Helix RADE until now.

The Design Mode command key equivalent for Shade Defaults is changed to CMD-D to avoid the conflict with macOS’s use of CMD-OPT-D for Show/Hide Dock.

Opening a collection or relation window in View by Icon mode, clicking in the gray area of the icon well, and pressing an arrow key would cause a crash. This has been fixed.

Likewise, pressing an arrow key in a window in View by Name or View by Kind mode in a window had no icons would cause a crash. This has been fixed.

The registration dialog would not allow the user to switch to another program, copy data, switch back and paste that new data into a field. This is fixed.

Helix 6.1.3 restores the original limitation of one open Apple Event process per licensed seat.

Helix RADE 6.1.4 is a renamed build of Helix RADE 6.1.3. It is functionally identical and is provided only to avoid confusion regarding which version is current.

If a collection or relation window is in list mode (View by Kind or View by Name) with a single icon selected, Helix RADE would crash if the window was toggled from Edit to Fast Find mode and then the Tab key was pressed. This has been fixed.

Diagnostic information, useful in facilitating field repair of damaged collections, has been added to Helix RADE. Because this information is of little use outside of collection repair, instructions on accessing it is given on a need to know basis.

Entering a single word (with no word separators) longer than 255 characters would cause Helix to crash. This has been fixed.

Deleting a record containing an index entry longer than 255 characters could cause Helix to crash. This has been fixed.

After selecting some records on a selectable list and opening the attached entry view, deleting a record should result in the next record (in the selection order) being shown. Instead the view was skipping over one and showing the next one beyond that. Continuing to delete repeats the pattern, deleting every other record. Eventually the entry view shows a clear form, but only every other record has been deleted.

This is a very old Helix bug, which is finally fixed. Helix now correctly shows the next record after one has been deleted.

Helix RADE 6.1.7 is a renamed build of Helix RADE 6.1.6. It is functionally identical and is provided only to avoid confusion regarding which version is current.

Using the Trim command on a template page now leaves a small border around the elements.

Helix RADE 6.1.9 is a fresh build of Helix RADE 6.1.8. It should be functionally identical to 6.1.8, but some users reported issues with 6.1.8, so we built a fresh copy from the source code.

Two changes were made for compatibility with macOS native Helix:

1. R7279: "When invalid..." controls for button options are now always shown in Classic RADE
2. User Editor terminology updated to match Europa (Helix 6.2) for Primary and Secondary users