A new public beta version is now available. If you’ve already installed b18 or later, you can simply choose Panorama>Check for Updates to install this update. If Panorama isn’t currently running, it will automatically offer to download b25 when you launch PanoramaX. If you haven’t installed b18 yet, you’ll have to use the Download Assistant as described in a previous post, or you can simply download it using this link:
This version includes minor bug fixes. The biggest change is invisible - this version was entirely created on an M1 Macintosh (though it does not yet contain M1 native code) and this version is notarized so that it can be installed on recent versions of macOS without having to use a special installation procedure.
- The datevalue( function now correctly handles the 31st day of August thru December.
- Date entry with missing year is now correct in November and December. If the year is missing, Panorama is supposed to default to a date between two months in the future and ten months in the past. This wasn’t working if the current date was in November or December, now it does. For example, as of today (Dec 9, 2021) dates of 1/15 or 2/15 will default to 2022, all other months will default to 2021.
- Fixed arrayrange( crash when the firstItem parameter is greater than the lastItem parameter.
- The arraydelete( function no longer crashes if the item number is out of the bounds of the array.
- Text funnels no longer crash if character range is backwards. (Previously, text funnel of [“z-a”,-1] would crash. Now it simply acts the same as 1, i.e. no funneling happens (but no crash).)
- A text funnel with start position of “-” or “≠” now works correctly, now these characters are only treated as a prefix if there are additional characters in the funnel specification.
- Fixed potential crash in calculating the length of a data cell.
- The ifselect statement now always sets info(“empty”) to false, whether anything was selected or not. This ensures proper operation of fills, etc. in the following code.
- When opening a damaged database, a specific error message is displayed for each type of damage.
- The calcenclosingrectangle statement now returns a sensible error if the formula doesn’t select any objects. Also, this statement now works correctly with a formula of “all” (for all objects).
- The fieldstotextvariables statement no longer chokes if a field name contains punctuation (for example a comma). Instead of choking, it now returns an error if any field name in the current database contains anything other than letters, digits or underscores. Note that this means that databases designed for web publishing should not use field names containing punctuation.
- Form objects that don’t contain code no longer indicate that code is triggered when they are clicked on. This was reported for tab panel objects, but it actually was true for all types of objects.
- Added extra error checking on the serverPingReply variable in the Database Options sheet.