Product
Support
Everything Else
Welcome To Helix 5.2
Introduction

15 January 2004--Welcome to Helix 5.2.1. This is a minor update release of the Helix 5 product family.This release contains bug fixes that have been incorporated into the code.

Helix 5.2.1 is a free update for owners of Helix 5.2 products. Existing Helix 5.2 serial number and key combinations work with this release. (Helix 5.0 and 5.1 keys do not.) The purpose of this release is to deliver fixes to bugs that were discovered after Helix 5.2 was released. There are no new features in this release.

About this release...

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

Although we are confident that Helix 5.2.1 is a solid release, it is possible that problems may be found that can result in collection damage. QSA ToolWorks will do everything in its power to support users who encounter errors caused by this software, but we cannot guarantee that problems do not exist. As always, please backup diligently.

Helix 5.2.1 includes the following bug fixes...
Corruption to fixed point data when loading from a logfile

Alert! A serious bug was found in Helix 5.2 and fixed in Helix 5.2.1. All customers using Helix 5.2 should upgrade immediately.

Fixed Point data was becoming corrupted after a crash when data entered since the last successful Save operation was imported into the collection from its logfile. Only data entered into a collection via the reading of a logfile after a crash was affected. Fixed Point data is now correctly imported from a logfile after a crash.

If you were not using the Save and Log feature, or you experienced no crashes in Helix 5.2, your data was in no danger whatsoever from this bug.

More details regarding this bug can be read here.

This bug was addressed by a patch program and updated Helix installers released on August 8, 2003. If you downloaded Helix installers on or after August 8, 2003, (or applied the patch) you already have this code fix.

Helix Client crash on launch

In Classic Mode, Helix Client would crash when it attempted to read the CLIENT_TCP_CONFIG file. Helix Client now ignores that file.

This bug was addressed by the patch program released on October 2, 2003. If you downloaded and applied that patch you already have this code fix.

Pasting a post icon with a linking Use From tile results in collection damage

A pretty rare combination: if an abacus containing a Use From tile was used as part of the target link, attempting to copy and paste the post icon would appear to work, but would actually result in internal damage to the post icon that would be reported as a “302” error by Update Collection. Helix now properly pastes structure that contains this construction.

Symbols for French Canadian currency display incorrectly

If the Numbers Control Panel was set to “French Canadian” when a new collection was created, currency symbols in that collection would not display correctly.

When a collection is first created, Helix copies the settings from the System’s Numbers format information and stores it in the collection itself in the itl0 and itl1 resources. Once a collection is created, changing the Numbers Control Panel has no effect on Helix. To modify the display of formatted data once a collection has been created, you must edit the itl0 and itl1 resources in the collection with ResEdit.

In the case of this bug, turning off the Leading Currency Symbol option (as is the default for French Canadian) would trigger the bug. Helix now properly handles the display of data with trailing currency symbols.

Fast Find (arrow key) paging of records works even if the equivalent Find command is removed from the user’s menus

In Helix 5.2 and earlier, the fast find keys are non-functional if Find permission is removed from the view permissions for a user. This is correct behavior.

The Fast Find keys also remain functional if the command key equivalent is removed from the Find nnn menu item. This is also correct behavior.

The bug was that the Fast Find keys remained functional even if the corresponding Find nnn command itself was removed from the menus altogether. Now if you remove a specific Find command, the arrow key equivalent for that command will not repsond.

Power Query recalculation was not aggressive enough

When a PowerQuery was cleared, internal code related to the previous query was not fully cleaned up. Helix is now more aggressive when a power query is cleared.

Typically this bug had no discernable effect on the end user, but it did result in unnecessary internal code that had to be managed by Helix Server. Fixing this bug should result in slightly better perfomance for Helix Client/Server.

Extraneous Why? messages during sequence errors

Previously, if multiple errors were encountered when running a sequence, the first error’s Why? message would open even when the On Error/Open Why? option was not checked. Helix now properly respects the status of the On Error/Open Why? status for each sequence.

Red letter warning text in Collection Info screen missing

In the Collection/Server Info window, RAMJet text was failing to turn red to indicate an undersized RAMJet. Helix now properly warns the users when the full collection is not loaded into RAMJet.

Old ‘off page’ pattern reappeared

When an entry view with a subform went from a record with multiple pages of subform data to a record with fewer pages, the ‘now missing’ pages were filled with the old dot pattern if you were viewing one of the lower pages for the record with more subform data. Helix now properly uses the new pattern in all instances.

Forward Delete key support incomplete

In many places in Helix, forward delete key supported was missing or incomplete. The Forward Delete key (fn-Delete on PowerBook/iBook keyboards) should now work in most situations where the Delete (backspace) key does.

•Previously, pressing the Delete key when the cursor was at the beginning of a line would generate a Why? message (“There is nothing to delete”) but a Why? message was not generated when the cursor was at the end of a line and the Forward Delete key was pressed. Helix now properly sets the Why? message in both instances.

•Pressing Command-Delete in certain places (e.g.: with a rectangle selected on a template) has always deleted the selected object. Command-Forward Delete now does the same.

•Pressing Option-Delete with a completed search statement selected in a PowerQuery has always removed that search from the query. Command-Forward Delete now does the same.

Minimum size of template rectangles reduced

In early versions of the Macintosh OS, attempting to draw a character in a rectangle (as defined on a template) that was too small to hold that character could result in a crash. This was resolved some time ago by Apple, but Helix was never updated to be aware of this fix. Now the 3 pixel (horizontal) buffer that Helix templates used to enforce to avoid crashes has been removed. (The minimum vertical height of a rectangle is unchanged.)

Minor Dialog Box errors

Spelling

“locution” has been corrected to read “location”.

Truncated Text

The word “Alignment” was truncated in some dialogs.

Misplaced Text

When called upon, the text messages “Each field will be placed in a separate record.” and “n consecutive fields will be placed in each record.” were being displayed in the wrong place in the import options dialog, overwriting other information. These messages now display immediately to the right of the record delimiter slot machine.

Command Key Equivalents

When a collection with Save and Log turned on was switched to Design Mode, one button in the dialog gives the option to open the collection in User Mode. The key equivalent for this button was still ‘c’ (for the old term Custom Mode). The key equivalent has been changed to ‘u’ with ‘c’ continuing to perform the same function (for users who have that key equivalent ingrained).

Global Font Call

In the dialogs that can be opened even when there is no collection open, the code was relying on global font data that is only available when a collection is open. These dialogs now calls the required fonts directly by name.

Color mini icon pictures muddy

The colorized mini icon pictures were hard to distinguish for some users. They have been cleaned up.

Paste Structure dialog uses black and white icons

The Paste Structure dialog was still using the black and white icons. It now uses the new color icons.

Update Collection diagnostic code values mixed up

Items 2 and 3 in the diagnostic code display were switched. They are now in the
proper order and display the information as originally intended.

Helix Utility allows compression at wrong time

Helix Utility previously would allow you to compress a collection immediately after a Data Damage Check or Data Damage Repair. This could lead to collection corruption. Helix Utility now requires you to close and reopen a collection that has been checked before compressing it.

Helix Utility drag and drop ignores some files

Previous versions of Helix Utility would not allow you to drag and drop a cracked (HEAV) or chipped (HEAQ) collection onto it. This has been fixed. (It may be necessary to rebuild your Mac’s Desktop Database file to enable this fix.)

Subform template’s father relation not reported

Subforms on templates were not indicating which relation they are in. Subforms now display the name of the relation using the format : template {in relation}

Option key not rechecked for nested/conditonal sequences

The status of the option key (for purposes of determining whether a sequence should optionally show dialogs) was previously tested only at the very beginning of the sequence execution. If the option key was held down when the sequence began, it was treated as ‘always down’ through the entire sequence chain. This behavior is unchanged.

With this fix, the option key is retested at the beginning of each nested or conditional sequence. If the option key is not held down when the main sequence begins, but is held down when a nested/conditional sequence begins, optional dialogs will be shown during the running of that nested/conditional sequence. The optional status returns to the default (based on the status of the option key when the main sequence was initiated) when the nested/conditional sequence ends.

This change enables you to enable the optional attribute only when necessary. For example, a sequence that exports data from a series of views is typically set to optionally show dialogs so the collection designer can preload the views with the required file names. If this sequence is built as a single long sequence that includes the ‘Export’ and ‘Close Window’ commands repeatedly, holding the option key down at the beginning requires the designer to respond to the export dialog box for every view in the sequence. However, by building this sequence as a separate sequence containing only the ‘Export’ and ‘Close Window’ commands, and then nesting that sequence in the main sequence, the designer can bypass the export dialog boxes for views that are already set, accessing only those that need work.

Apple event retrieve skips document fields

Prior versions of Helix skipped over document fields completely when retrieving records via Apple events. Beginning with Helix 5.2.1, the logical file path to the document is returned when a document field is encountered.

Data retrieved from a Helix collection via Apple events may now include extra elements the programmer did not take into account before. If you rely on external access to a Helix collection, be sure to consult with the person responsible for the external access programming before updating to Helix 5.2.1.

The internal Apple event version number has been incremented from 2.0 to 2.1. However, this version number is not accessible at this time. To determine which version of Helix (and therefore which version of Apple event access) is running, use the get version command. Since this change is implemented in Helix 5.2.1, testing the Helix version
itself tell you whether you have access to document fields or not. In AppleScript the statement
(get version ≥ 521)
will return
true
if documents are returned and
false
if they are not.

Event timer

Originally added for testing purposes, an internal event timer has been cleaned up and made available to collection designers. Press CMD-Control-Option-T to activate it. (Close the timer window to deactivate it.)

The timer window reports the minutes, seconds, and ticks (60ths of a second) an event takes. An event is defined as a menu selection or sequence button click. The elapsed time for each event automatically displays as long as the timer window is open.

The Event timer is not an official feature and is being made available ‘as is’ for designers who want to test the speed of Helix under certain conditions. As it is, it has a few of limitations:

  1. The event timer window does not respond to Command-W: you must click the window’s close box to close it.
  2. When the event timer is the frontmost window, Function Key commands are unavailable. To time a menu item that has a Function Key assigned to it, either select the item directly from the menu or bring any other window to the front before pressing the Function Key.
  3. The event timer ignores keystrokes in an open window, so pressing Enter to trigger a default sequence will not start the timer. Clicking the sequence’s button will properly start the timer.
  4. When an asynchronous list is opened, the event timer records the amount of time required to open the view, not the amount of time it takes to locate and display the records.

The timer reports each discrete event: it does not accumulate time as new events occur.

Newly Discovered Known Problem with Workaround

Find and Print All with an option-4 post on print error

A bug has been discovered that occurs during record printing if and only if you have all of the following conditions at the same time:

  1. The view is an entry view
  2. You use “Find and Print All” to print the records
  3. There are multiple records to be printed
  4. The view includes a subform
  5. At least one of the host view records has enough subform data to require
    more than a single page
  6. The view is set to Post on Print
  7. The post is an Option 4 post designed to delete the host record

In this situation, the records print properly until the first multipaged record is encountered. After that record is printed, subsequent host records are deleted before they are printed, and their pages are printed with no data.

This bug can be avoided in one of two ways:

  1. Make the host form into a list and use “Print Form” instead of “Find and Print All” to print.
  2. Create a recursive sequence with “Find First” and “Print Form” commands and use that to print.

This bug has existed in Helix for a very long time, but it was only recently discovered and is being documented here for the first time. If you have never encountered it before, you do not need to worry that your collections have changed behavior due to a Helix version upgrade.

5.2 Release Announcement
Helix 5.2 debuts, giving users an early-bird opportunity to use features and fixes slated for Helix 6
FOR IMMEDIATE RELEASE

2003.06.09--Helix Technologies today announces shipment of Helix 5.2, the second feature update of the Helix 5 product family. The new release, which has been in development and testing for several months, includes some long-awaited new features and enhancements that were initially slated to be included in Helix 6, the much-anticipated Helix macOS product.

One of the original Mac tools evolves
Helix was originally billed as a "databased information management system" when it made its initial appearance just after Thanksgiving in 1984 as one of the original Macintosh software offerings.

What began as a personal software construction kit evolved into a tool used by many thousands of individuals and businesses in nearly fifty countries and a hundred different industries. "Despite an almost total lack of advertising and promotion over nearly 20 years, the Helix product family has been one of the bedrocks of Macintosh computing," says Helix Recovery Team co-director Gil Numeroff, adding that "we're finally poised to move beyond the Macintosh cradle and take our rightful place among the truly innovative software development tools that have been produced since the dawn of personal computing."

Helix was one of the first Macintosh products to cross platforms back in 1987 when Apple and Digital Equipment Corporation (DEC) first created an alliance to promote their products. Helix VMX ran on Digital's VAX platform and was widely lauded as a tool far ahead of its time. But the debut of the Macintosh IIfx in 1990 and a court's decision not to punish Microsoft for its outright theft of the Mac OS helped bring about the demise of both Helix VMX and the VAX as a development platform. Odesta Corporation, Helix's creator and owner at the time, was left with a strong distaste for cross-platform operation and withdrew into its Mac-only cocoon, where Helix remained in spite of desperate pleas from its user base to expand its frontiers.

The more time passed, the deeper into its corner Helix painted itself, and by the debut of Windows 95, the job of modernizing its code appeared nearly impossible. When The Chip Merchant took over the reins in 1998, it promised to fix all of Helix's known problems, make it work under TCP/IP and bring it to macOS and the Windows and Linux environments.

A stagnating computer industry and the attack on the World Trade Center in 2001 eventually brought the company down to a point where it had to go on "hiatus," falling critically short of its stated goals. That hiatus lasted until the following summer when the "Helix Recovery Team" sprung into operation.

A groundswell of support from Helix users around the world helped put Helix back on its feet. By late fall of 2002, the team had released Helix 5.1, a maintenance upgrade that provided fulfillment of a lot of wish-list items that had been around for years.

The long road to macOS and beyond
Buoyed by the success of 5.1, the Team decided to press forward and bring Helix to macOS in the form of Helix 6, a project that was clearly much bigger than the one they had just completed.

The critical first step, and the one on which everything that followed would depend, was to take the work that had just been completed and build it in a more modern environment: Code Warrior 8.3, the current computer industry standard. Helix's code base was so old that development was being conducted under a much older version of Code Warrior and it was clear that unless the Team could dig in and get that job done, there would be no future for Helix.

Starting the day after 5.1's release in December 2002, the transformation began. By the middle of March, it appeared that the laborious process would soon bear fruit. Along the way, the Team began to add several of the features on the Helix 6 list.

By April, Helix was--while still an OS 9 product--up and running and loaded with a raft of features and fixes that users had been asking for. "Taken together with what we did in 5.1, and all the things that were added to Helix since 4.5.5, we felt we had reached a turning point," said Numeroff. "The question for us was whether we should make our users wait until we finished Helix 6, or offer them the chance to start using these tools right away."

In the end, the choice was obvious. "Helix 5.2 represents the state-of-the-art for Helix," said Numeroff, "and users who have waited for a macOS product since 1999 were beginning to get 'antsy' for more functionality. The Gulf War this spring and the general downturn in the economy, combined with the magnitude of the task of modernizing the Helix code base has resulted in the debut of Helix 6 being pushed further into the future, so we needed to do something now." If pre-release upgrade sales are any indication of the merits of this decision, Numeroff believes it was the right one.

The release date bears some significance for the Helix Recovery Team. June 9, 2003 marks the end of its first year managing the day-to-day operations of Helix.

"The road to Helix 6 is still a pretty long one," said Numeroff, "and some pretty vocal segments of our user base have been clamoring for some of these features for a long time, so we decided not to make them wait any longer."

Here's what's new in Helix 5.2
QuickTime Support

Document Content Display Capability Expanded

QuickTime Display of Still Image Formats
Helix 5.2 uses the QuickTime engine to render the contents of still image documents when they are placed in a Picture tile. Because of this, Helix can now display images in virtually every popular still image format. The types of files Helix can display will grow as Apple enhances the QuickTime specification. The current list of supported file types can be seen at

http://www.apple.com/quicktime/products/qt/specifications.html

Format support depends upon the version of QuickTime installed
Apple continues to add new formats to each revision of QuickTime. If you are unable to view certain types of documents on some computers, but they are viewable on others, the problem is probably related to an older version of QuickTime installed on that computer.

Keep in mind that Helix can only display still images, so time-based formats like animated GIFs, Motion JPEG, AVI, etc. are not supported at this time. If Helix can not display the contents of a file, the text “Document format unsupported” will be displayed in its place.

One startling omission in image support is for Acrobat (pdf) format. QuickTime 5 doesn't seem to support it, and apparently QuickTime 6 doesn't either.

No code changes necessary
You do not need to make any changes to your Helix applications to take advantage of this new functionality. In any place where a Picture tile could display the contents of PICT and EPS files, JPEG, TIFF, GIF, and all of the other supported file types will now display. Because rendering is done ‘on the fly’ there is no need to revisit previously entered records, or to do anything at all. The file’s contents will automatically be displayed when possible.

Internal and External Document Support

The new code works with both internally and externally stored documents. External documents must contain a path that can be resolved by the machine on which the file is displayed. External documents can be stored on any mountable volume: a network server, a mounted CD, or any other type of storage device that appears on the desktop as a volume.

If a document can not be displayed, whether it is because it is in an unsupported format or because it is an external document whose path can not be resolved, the text “Picture Not Available” will be displayed in the data rectangle.

Note that the contents of the document are not immediately displayed when it is specified, or even when the field is tabbed out of. The record must be entered before Helix can display the image.

Furthermore, because the rendering of the document occurs on the Client, not the Server, the path to the document must resolve on the Client machine. Requiring the Server to render and pass the data to the Client would result in severe perfomance degradation.both to the Helix Client/Server environment and to the network.

Memory Notes
Because Helix can now render images of significantly larger documents, you may need to adjust your memory settings upward. For Helix RADE, Engine, and Server,

5xxx errors indicate that you need to increase the data cache and 7xxx errors indicate that you need to increase the structure cache. We recommend that you increase your caches by no more than 2MB at a time — try to keep it as low as possible, but not so low as to induce crashes. Please consult the technical support documentation related to memory settings on our web site for more information.

Fixed Point Data Type Extended

The Fixed Point data type now supports numbers in the range of +22,517,998,136,852.47 to -22,517,998,136,852.48 (aka ±22.5 trillion). Previous versions of Helix were limited to a range of (approximately) ±10 million.

No code changes necessary
You do not need to make any changes to your Helix database to take advantage of this new functionality. Fixed point fields that previously were limited to a range of ±10 million will automatically support a range of ±22.5 trillion.

Helix Utility and Update Collection Automation

Major enhancements to the Apple event suite of both of the Helix utility programs enable programmers to build collection checking into custom applications. Complete AppleScript dictionaries bring that power into reach for everybody.

Helix Utility now supports drag-and-drop collection opening. When you drag a collection onto Helix Utility, the “Open Collection” command is executed. The standard warnings will be presented, exactly the same as if you had launched Helix Utility and selected “Open Collection.”

After installing Helix Utility version 5.2, you may have to rebuild your desktop database file to enable drag and drop functionality.

For more information on automating use of Helix Utility, see next section.

Advanced Diagnostic Support

Helix Update Collection also includes the ability to generate output in the event of a failed collection. This support was added to aid Helix Technical Support in diagnosing damage in the field, minimizing repair costs. When a collection is “not corrected” by Update Collection, a diagnostic code will be displayed in the lower left corner of the dialog. Contact technical support with this code and we can quickly determine the approximate seriousness of the error.

Movable Modal Dialogs

Virtually every dialog box in Helix is now of the movable modal type. If a dialog is obstructing an item on the screen, you can move it out of the way.

Application Switching Allowed
You can switch out of Helix to another application when a movable modal dialog is active. However, you must respond to the dialog before you can do any further work in the Helix application itself.

Document Icon Is Now Application Specific

The icon that represents a document is now the correct icon for that file type. The icon is stored internally, and is drawn from the local computer’s icon database. If the application that created the file can not be found, or its icons are not in the local computer’s icon database, the standard generic icon will be used.

The current icon is the 1 bit (black and white) version of the document’s icon. This will be addressed in a future release.

Location Hints

In all slot machine lists where it makes sense, the name of the relation where the icon is found is shown. They are:

  • User Editor: view
  • Use From tile: template
  • Sequence Editor: views (both in selection list and in the sequence step list)
  • Get Info: reference list [added in version 5.1]
Edit Keys Work in Text Edit Mode

In prior versions of Helix, the Edit Keys (Page Up, Page Down, Home, & End) did not work when the cursor is active in an editable text field. This has been fixed.

Multiprocess Friendly

Helix will no longer hog processor time. This will give background tasks (such as printer spooling software) processor time, so they can work more smoothly with Helix.

Sequence Editor List Shows Step Type

A picture is worth a thousand words...

AppleScript (and Apple event) Improvements

Significant improvements will enable a user to:

  1. Cleanly shut down a server (no more "Abandon Users" dialog on the server because Joe forgot to quit Helix Client when he went home for the day)
  2. Automatically reopen a Collection after running the Helix Maintenance utilities.
  3. Additional benefits to be detailed in the Release Notes when 5.2 ships.
Functionality Changes

Helix 5.2 includes the following functionality changes that improve the usability of Helix, but do not quite qualify as new features:

Template Object Manipulation

Deleting Rectangles
Rectangles on a template will no longer delete when resized down via keyboard commands. (CMD-delete and deleting via mouse drag still work.) Attempting to delete a rectangle via keyboard resizing now sets a Why? message explaining that it doesn't work, and explaining the proper methods of removing them.

Resizing Subforms
It has never been possible to resize a subform directly on a template. (You must open the subform’s own template and resize it there.) Even so, subform rectangles included a size box in the lower left hand corner, implying that resizing was possible.

Subform rectangles no longer display the size box. In addition, attempting to resize a subform via keyboard commands now sets a Why? message explaining that this is not possible.

Proportional Scroll Boxes

Primary Window Scroll Boxes
The Scroll Bars that control the primary window area (e.g.: the window itself) now display Appearance Manager compliant proportional scroll boxes in User Mode.

Data Rectangles
Scroll Bars (when defined) in text rectangles now display Appearance Manager compliant proportional scroll boxes.

Slot Machines
Scroll Bars (when appropriate) in slot machines (the selectable lists in dialogs, etc.) now display Appearance Manager compliant proportional scroll boxes.

Modernized Appearance

Abacus and Post Tiles
Abacus and Post tiles are colorized with the macOS gray bar background pattern style.

Templates
Template editor appearance has been modernized. This was done primarily to avoid the distortion that occurs when running RADE in the Classic environment under macOS.

Views
The "off the page" area in view windows now displays a diagonal variation of the macOS 'gray bar background' style.

Unrecognized User Prompts Legal Notice

In version 5.1 (and all previous versions), the chatty greeting that appeared when an unrecognized user name was entered ("I'm sorry, we haven't been introduced. Please at least pretend to be someone I know.") was replaced by a more formal message: "You cannot access this system without a valid user name. Please check your user name and try again."

A security consultant and a legal expert have pointed out to us that the second sentence above undoes the legal benefit of the first by seeming to invite a potential hacker to keep trying. In a court of law, unless the appropriate wording is displayed in this situation, you may be unable to press charges against someone you catch attempting to break into your system. Thus, in Helix 5.2, this second sentence has been replaced by the four appropriate words: "Unauthorized access is forbidden."

In situations where security is an issue, particularly with collections being served via TCP/IP, QSA ToolWorks strongly recommends that you turn the “User Name Security” feature on.

RAMJet Statistics

The Server Information window includes statistics regarding RAMJet usage. In earlier versions, this information was not easy to interpert. Display of RAMJet statistics is now much more intuitive.

When RAMJet is set too low to load the entire collection into RAM, the text will be displayed in red. The percentage figure tells you how much of the collection is loaded into RAMJet and the MB figure tells you how much more memory needs to be allocated to Helix so the entire collection can be loaded into RAMJet.

When RAMJet has sufficient memory, the text will be displayed in black, with the free space is expressed in MB. If the cache is close to full, a percentage will also be displayed, letting you the percent over the required amount. Typically you want RAMJet set so that you have about 10% overhead. This gives your collection room to expand as data is added.

Compiling Forms Dialog Politeness

When you select "Compile Forms" it no longer displays a thermometer if there are no forms to compile. The message "Now compiling form 1 of 0" should never appear again. This was disconcerting (and vaguely annoying) in Server and Engine, where the dialog would flash every time a collection was opened.

Client Structure Saved on Log Off or Abandon

In previous versions of Helix, logging clients off via the “Client Info” window or quitting and abandoning clients resulted in the loss of the client’s structure file.

Beginning with Helix 5.2, Helix Client will first determine whether the user was working from a saved structure or not. If they were, the structure will be saved silently, with no prompt asking them to save changes to the structure. If they were not working from a saved structure file, Helix Client will quit silently, and the user will not be prompted to save a structure file.

It is important to keep in mind that these are administrative functions and as such assume a level of expertise that is commensurate with the responsibility. Logging users off or abandoning them immediately terminates their access to the Helix Server and no opportunity is given to the end user to finish entering partially completed forms.

Demo Version Importing

The demo versions of Helix no longer disable importing. This limitation rendered some demos unusable, so we removed it.

Bug Fixes

Helix 5.2 includes several bug fixes, along with a significant internal change that is required to move Helix to macOS and beyond.

Command Keys In Get Info Window

Long ago in a version far away, it was possible to select an item in a Get Info window’s list of referenced icons and then press Command-O or Command-I to invoke the appropriate action. This functionality has been restored.

Entry Rectangle Editing Crash

Fixed a minor bug (also present in the current shipping version) where setting the format of an entry rectangle to the default value could cause the program to crash.

Task Management Crash Avoidance

A code error was found that could (in rare instances) cause Helix to lose track of a process, resulting in an apparently random crash. Another error was found that could (in rare instances) cause Helix to crash when a view with a subform with a summary operation was open in the background and a post occurred that caused the background summary to reevaluate. (This was fixed in 5.1.1).

Apple Event Ready Reply’s Reported Delimiters

If delimiters are deselected in a view, Apple event selector 120 (“Done”) would return the previously selected delimiters anyway. It now returns the proper (empty) delimiter(s) selection.

Apple event Post on Retrieve

An Apple event bug introduced in Helix 5.0 related to post on retrieve was fixed.

TCP/IP Code Initialization Error

In Client/Server, a bug was fixed that caused Server or Client to fail if it was quit and relaunched without opening (or visiting) a collection.

Helix Utility

The "Loading into RAMJet" dialog was lost in version 5.1. It has been restored.

Compiled with CodeWarrior 8.3

This version is compiled with CodeWarrior 8.3, the latest tools available from Metrowerks. Consequently, portions of the code had to be revised to compile correctly.

As noted elsewhere on this site, this seemingly insignificant detail was actually the first and most important step on our road to Helix 6. While it presents no apparent benefit to the end user, if we were unable to accomplish this part of the project, there would be no future for Helix.