Header

AstroPlanner Beta Testing

Introduction

Anyone is free to download and test the latest beta version of the application. Please note that beta versions of the application have a built-in expiration date that is 120 days after the release date. After that date, you can still use it, but you'll be "nagged" to download a more recent release. This is to prevent bugs being reported on older beta versions that have already been fixed in later releases.

Please discuss beta issues only on the Beta Testers mailing list. Click here to join/leave the list.

Click here for more information on how to report a bug.

V2.4 Notes:

This page last modified: 2024/05/09 10:25 (Pacific time)

Download

VersionRelease DateExpiry Date
2.4fc12024/05/03120 days from Release Date

Macintosh

64-bit Application (.dmg)Download160.9MB64-bit version. Intel-based Mac with MacOS 10.14 or later. Apple Silicon-based Mac with MacOS 11 or later.
64-bit Application (.dmg)Download107MBSpecial version for MacOS 10.11 through 10.13. Intel-only.

Windows

32-bit Application (.exe)Download92MiB32-bit version. Installer. Windows 8.1 or later
32-bit Application (.exe.zip)Download91.5MiB32-bit version. Zipped installer
64-bit Application (.exe)Download87.9MiB64-bit version. Installer. Windows 8.1 or later
64-bit Application (.exe.zip)Download87.4MiB64-bit version. Zipped installer
64-bit Application (.exe.zip)Download143.7MiBSpecial 64-bit version for Windows 7 SP1 through 8.0.
32-bit Application (.exe.zip)Download153.1MiBSpecial 32-bit version for Windows 7 SP1 through 8.0.

Both platforms

User Manual (.pdf.zip)Download82.8MiBV2.4 beta user manual

Note: Beta versions of the application typically do not include the user manual or scripting manual in order to reduce download size.

Release Notes

A list of unresolved bugs can be found here, and feature requests here.

Version: 2.4fc2
Release Date: Soon
Fixes: 6, Enhancements: 0

ID:
7827

Status:
Fixed

Date:
2024/05/08

Notification.!KillAsyncTimer: NilObjectException

Version: 2.4fc1
Expires: 01/09/2024
Date: 08/05/2024 08:53:59 BST
OS: Windows 11.0.22631 (X86)

Exception Type: Nil Object Exception

1: Sub Notification.!KillAsyncTimer( Timer )
2: Sub App.Event_Closing()

Resolution:
Fixed.

ID:
7828

Status:
Fixed

Date:
2024/05/08

Application does not like Fix/Unfix date/time

Fixing the date/time (or subsequently unfixing it) causes the responsiveness of the application to decline precipitously. The UI is unresponsive for a while, but then regains its responsiveness. The more objects in the object list, the worse it becomes.

Analysis:
This is an issue with Windows threading priorities.

Resolution:
Fixed.

ID:
7822

Status:
Fixed

Date:
2024/05/04

MainWindow.ResizeStuff: UnsupportedOperationException

Exception Type: UnsupportedOperationException
Exception Message: ResizeStuff. Debug=A B C D E F I J

1: Sub MainWindow.ResizeStuff( MainWindow, boolean )
2: Sub MainWindow.WidgetsRearrange( MainWindow )
3: Sub MainWindow.WidgetsTabChange( MainWindow )
4: Sub MainWindow.TabsChange( MainWindow )
5: Sub MainWindow.tabs_PanelChanged( MainWindow, DesktopPagePanel )
6: Sub DesktopPagePanel._SetSelectedPanelIndex( int64 )
7: Sub DesktopPagePanel.SelectedPanelIndex.Set( int32, int64 )
8: Sub MainWindow.CurrentTab.Set( MainWindow, int32, int64 )
9: Sub MainWindow.APTools_ButtonClicked( MainWindow, APToolbar, int64, int0(), w.MainWindow.BarItems, boolean )
10: Sub APToolbar.ClickTimer_Action( APToolbar, Timer )
11: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Clicked on AstroPlanner plan entry and the error was generated.
message=ResizeStuff. Debug=A B C D E F I J


Resolution:
Fixed.

ID:
7823

Status:
Fixed

Date:
2024/05/04

Jumpy observation database

This was fixed some betas ago, but it is back since at least b27:

In the Observations tab, double click to open an observation in the observation database. Result: the session in which the observation was logged is selected but not the applicable observation but the first observations of the session instead.

In the observation database, open (edit) an observation, make any changes and save the observation. Result: the first observation in the session is selected and the list of sessions scrolls all the way to the bottom, even though the correct session remains selected.

As far as I'm concerned, this is the only "show stopper" for V2.4..!


Resolution:
Fixed.

ID:
7824

Status:
Fixed

Date:
2024/05/04

Switch to tab greyed out

The options to switch the applications tabs in the Edit - Switch to Tab menu are greyed out. Shortcut keystrokes not working, either.
Screenshot attached.

Attachment: VAvW 2024-05-04 om 11.53.53.jpg

Analysis:
The current software changed the way menus are enabled/disabled. I missed updating this sub-menu.

Resolution:
Fixed.

ID:
7825

Status:
Fixed

Date:
2024/05/04

More greyed out menus

Just noticed that more of the application's menus are greyed out, per attached screenshot.

Shortcut keys, such as Cmd+C to copy objects, are not working either.

Attachment: VAvW 2024-05-04 om 16.00.16.jpg

Analysis:
The current software changed the way menus are enabled/disabled (I suspect a framework bug). I missed updating these items in some cases.

Resolution:
Fixed. Bonus: Edit > Cut works on Object List.

Version: 2.4fc1
Release Date: 2024/05/03
Fixes: 26, Enhancements: 4

ID:
7820

Status:
Fixed

Date:
2024/05/03

Files names containing [brackets] not fully displayed by application

All of my planfiles contains brackets [ ] in their names, for example: "Andromeda [12-14].apd" for objects in Andromeda for 12-14" telescopes, "Andromeda [8-10].apd" for 8-10" scopes and "Andromeda [5-6].apd" for 5-6" scopes.

Some time in the (recent) past AstroPlanner stopped displaying any text between brackets in the top of the application window. This means that whenever multiple planfiles are open for various list in one constellation (the abovementioned ones, but a filename like "Andromeda [Burnhams]", too) all of these files in the top bar of the application as well as in the Window menu (showing currently open planfiles) are displayed as "Andromeda". This makes it impossible to differentiate between the different files, unless they're brought to the front.


Resolution:
Fixed.

ID:
7821

Status:
Fixed

Date:
2024/05/03

Clicking rows on the object list can overwrite data

If you click a row of the object list too fast after another row was selected, the object data can be overwritten by the previous object's data.

Resolution:
Fixed. (Hopefully. I can no longer reproduce the issue)

ID:
7819

Status:
Fixed

Date:
2024/05/02

Extremely slow selection of objects

Selecting objects in the object list can be extremely slow, especially. on Windows, and slower computers. To mitigate this, perhaps the drawing of images and/or constellation maps can be done in the background to improve responsiveness.

Resolution:
Fixed.

ID:
7786

Status:
Fixed

Date:
2024/04/30

When Choosing to Replace IDs with Search Terms, Synonyms have the ID "Synonym"

Looks like this has popped up again.

Steps to duplicate:

1. Make sure the NGC and PGC catalogs are installed.
2. In a new document choose New Object.
3. In the ID field, put in "MCG 6-3-18". Check Synonyms and click All.
3. Select "Replace ID with search term"
4. Choose the NGC 404 object and then Add Selected.

Note that the ID for the new object is "Synonym". It should be MGC 6-3-18.

Resolution:
Fixed.

ID:
7817

Status:
Fixed

Date:
2024/04/30

Sort List only uses one level of information to sort (used to sort by up to three levels)

Sort List only uses one level of information to sort (used to sort by up to three levels)


Analysis:
The reason for this is that if you select a continuous value field (say R.A.), then any further sub-fields would (in theory) be redundant. If you choose a discrete value field (say Visibility, # Observation, etc.) then the subsequent sub-field would be valid.

Resolution:
Fixed. The fields are no longer disabled, but a warning is now shown if you pick a continuous value field followed by another field.

ID:
7810

Status:
Fixed

Date:
2024/04/30

Data from user field ported to next observation: time vs. previous object logged

When entering observations logged in succession, data from any user fields is ported to the next observation, which is very nice.

When entering observations in quick succession, for which the same date & time is used, I noticed the user fields as entered for the first observation in time in that sequence, is always ported to the other observations added sequentially. That means that, if for example the first observation in the sequence was a galaxy pair for which I notes (in a user field), "all members observed", that "all members observed" field is used for all following observations logged at that same moment in time. That requires that user field to be edited for all following observations at that same time that are not galaxy groups.

It would be better if the user fields were ported from the *previously logged observation* in the database, instead of from the first observation logged at a specific time.

Nothing major, it does not hamper the usability of AP at all, just a thought for a small improvement.


Resolution:
Fixed. Untested.

ID:
7747

Status:
Fixed

Date:
2024/04/30

ObjectList_MenuAction: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub MainWindow.ObjectList_MenuAction( MainWindow, ObjectListbox, string, string, string )
2: Sub AddHandler.Stub.63( string, string, string )
3: Function StripedListBox.ServiceMenu( DesktopMenuItem ) as boolean
4: Function StripedListBox.Event_ContextualMenuItemSelected( DesktopMenuItem ) as boolean


User description of above error trace:

I had highlighted the object with ID OCL352 in the attached file. I right-clicked on it and chose Show in Catalog. That's when this error occurred. It now shows 2 objects selected in the Title Bar, which I don't remember doing (OCL352 and Sh2-90).

Attachment: Names 2.apd

Resolution:
Fixed.

ID:
7669

Status:
Fixed

Date:
2024/04/30

MainWindow.Event_CancelClosing: Nil Object Exception

Exception Type: Nil Object Exception
Exception Message: @ M

1: Function MainWindow.Event_CancelClosing( MainWindow, boolean ) as boolean
2: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

I downloaded 3 contributed plans, the first one (Planetary Nebula Club) was opened in the Objects view, I changed the order of some columns, and when saving the plan, I got the error.
The other 2 plans were apparently still waiting to be downloaded.

Resolution:
"Fixed". Not fixed, but extra code added to help narrow down the cause.

ID:
7816

Status:
Fixed

Date:
2024/04/29

PositionWindow.SavePosition: RuntimeException

Exception Type: RuntimeException
Exception Message: 'VerticalOffset' is not a previously-saved variable!
Exception Number: 1

1: Sub Data.Operator_Lookup( string )
2: Sub PositionWindow.SavePosition()
3: Sub PositionWindow.Event_Closing()
4: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

In Preferences, I toggled "Open documents in full screen" (from on to off), the closed the Preferences window and this exception popped up.
number=1
message='VerticalOffset' is not a previously-saved variable!


Resolution:
Fixed.

ID:
7815

Status:
Implemented

Date:
2024/04/28

Double click to move FoV

Without giving it any thought, I just double clicked to move (re-center) the FoV but nothing happened. That made me realize that it is no more than a natural movement to have to FoV center on a position that is double clicked in the FoV. Would make for a nice enhancement.


Resolution:
Implemented. Took all of 30 seconds...

ID:
7811

Status:
Fixed

Date:
2024/04/23

Issue with Windows numeric fields

In Windows, newly initialized numeric fields show their value in red (i.e. illegal value) even though the value is legal (numeric and in range).

Resolution:
Fixed.

ID:
7771

Status:
Fixed

Date:
2024/04/23

MainWindow.ObjectList_PaintCellText: Nil Object Exception

Exception Type: Nil Object Exception

1: Function MainWindow.ObjectList_PaintCellText( MainWindow, ObjectListbox, Graphics, int64, int64, int64, int64 ) as boolean
2: Function StripedListBox.Event_PaintCellText( Graphics, int64, int64, int64, int64 ) as boolean
3: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Open a saved plan or open a saved plan and change observing sites. Occurs on Ventura and Sonoma.


Resolution:
"Fixed". Added code to help track this down.

ID:
7809

Status:
Fixed

Date:
2024/04/23

MCG designations missing from updated Hyperleda catalogue

The updated Hyperleda galaxy is a treasure trove, so much worthwhile information just a mouse click away.

Yet, something has changed to the catalogue that is perhaps a bug, perhaps just the catalogue itself. Per attached screenshot: the MCG designations for galaxy, the were previously included in the objects notes in that catalogue, have gone missing. Would be very nice to get them back.

Resolution:
Fixed. New release of catalogue includes all known IDs in the PGC, Name, or Notes field. Sorry, adding extra indexed ID columns causes serious bloat, so they were not implemented.

ID:
7808

Status:
Implemented

Date:
2024/04/21

Duration of observing session displayed in Observations tab, in addition to Observations logged

Currently, the number of observations logged in a session is displayed in the Observations tab, per attached screenshot. Would be a nice addition if the duration of the session (hours + minutes) were displayed, too, both for sessions that have ended and for sessions to which observations are being added.

I am working out observations as I type this and I thought it would make for a nice enhancement.

Attachment: VAvW 2024-04-21 om 11.19.22.jpg

Resolution:
Implemented. Took all of 30 seconds...

ID:
7782

Status:
Fixed

Date:
2024/04/19

App._ImportObservationFile_Action: InvalidArgumentException

Exception Type: InvalidArgumentException
Exception Message: No column with name AssociatedData

1: Function RowSet.Column( string ) as DatabaseColumn
2: Sub PlanObservation.Constructor( RowSet )
3: Sub ObservationFunctionality.Import()
4: Function App._ImportObservationFile_Action() as boolean
5: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Importing observations


Resolution:
Fixed.

ID:
7788

Status:
Fixed

Date:
2024/04/19

Issue with Comet/MP cache file

Regarding the asteroid/comet cache file then this happens on every restart of AP. It does not resolve itself; it can’t delete the cache files. Also, if I look at which process is locking the asteroid cache file then it is AstroPlanner itself. The comet cache file can be deleted but was obviously locked at some point. AP is running under normal privileges. Is this a problem for only me? My guess is that it is the Xojo framework not releasing the file. Can you strip the read-only attribute of the file and then delete? Pretty radical 😊 but as it should just be you holding the file handle then most probably safe, or maybe not

Resolution:
Fixed.

ID:
7404

Status:
Fixed

Date:
2024/04/19

Clock Offset crashes 2.4b13

I'm based here in the UK. Observatory computer is currently running at British Summer Time, which is currently 1 hour ahead of UT. I also observe using iTelescope in New Mexico which is -6 hours behind UT. If I choose the iTelescope location as my observing location and add -6 hours in the clock offset box and set my UK location in the 'Clock offset from site' box. Astroplanner crashes with the following error.

Version: 2.4b13
Expires: 24/12/2022
Date: 04/09/2022 11:00:16 BST
OS: Windows 11.0.22000

Exception Type: Nil Object Exception.

Without the Clock Offset feature working , If I want to choose the New Mexico location, I have to manually fix the observing time in New Mexico in the Date and Time boxes in order for the everything to work. Obviously I cannot run AP in live mode beacuse as soon as I untick the Fix date box, the time displayed is no longer New Mexico time, but my UK location.

Analysis:
I bypassed this issue since I couldn't reproduce it. However I have now (finally) reproduced it and fixed it.

Resolution:
Fixed.

ID:
7805

Status:
Fixed

Date:
2024/04/18

Sorting by Magnitude won't Allow Secondary Sorting

There are many objects with the same magnitude so this should allow you to continue sorting after going by Magnitude.

Steps to Dupe:
1. Open the attached document.
2. Choose to show Editing fields.
3. Click the Sort List pop-down and choose Sort By
4. Choose to sort by Magnitude in the top field.

All the other fields now go gray.

Attachment: Companion Objects.apd

Resolution:
"Fixed."

ID:
7802

Status:
Fixed

Date:
2024/04/18

DateExtensions.AsDateTime: InvalidArgumentException

Exception Type: InvalidArgumentException
Exception Message: Month out of range

1: Sub DateTime.Constructor( int64, int64, int64, int64, int64, int64, int64, TimeZone )
2: Function DateExtensions.AsDateTime( extends Date ) as DateTime
3: Sub APDateControl.Value( assigns Date )
4: Sub PlanWizardDialog.OpenStuff( PlanWizardDialog )
5: Sub PlanWizardDialog.OpenTimer_Action( PlanWizardDialog, Timer )
6: Sub DesktopWindow.ShowModal( DesktopWindow )
7: Sub App.NewPlanCreationWizard( MainWindow )
8: Function App._FilePlanCreationWizard_Action() as boolean
9: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Opened Plan creation wizard in an unregistered copy of Astroplanner. The system produce the application exception message.. If I select continue, Astroplanner close
message=Month out of range


Resolution:
Fixed. Not sure what is going on here, but I have added code to track it down if it happens again.

ID:
7800

Status:
Fixed

Date:
2024/04/18

FindCityDialog.FindCity: Out Of Bounds Exception

Exception Type: Out Of Bounds Exception

1: Sub FindCityDialog.FindCity( FindCityDialog )
2: Sub FindCityDialog.TypingTimer_Action( FindCityDialog, Timer )
3: Sub DesktopWindow.ShowModal( DesktopWindow )
4: Function PositionDialog.Modal( DesktopWindow ) as sitionDialog.Clicked
5: Sub ResourcesWindow.FindPlaceBtn_Pressed( ResourcesWindow, PDPushButton )
6: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

searching for a place in Spain


Resolution:
Fixed. I think I fixed this. If not I have added code to help hunt it down next time it happens.

ID:
7806

Status:
Fixed

Date:
2024/04/18

Fix for menu item enable bug

There's a bug in the latest compiler framework that enables all menu items, whether or not it's applicable.

Analysis:
I'll have to put in a mess of code to work around this.

Resolution:
Fixed.

ID:
7799

Status:
Fixed

Date:
2024/04/18

Event Scripts

The Event Scripts... setting Enabled->Global does not appear to work correctly. An event that is marked Global is not available and executed by all plan documents, but rather the same as Local and is only available in the current plan.

Creating a Global, When plan document is opened, myscript only works in the current document. Restarting AP and opening a different document does not run the global script and the opened document does not have a reference to the event in Event Scripts...

Resolution:
Fixed. Also revised the Script Event dialog to make it more logical and allow for both a local and global script to run for a given event type.

ID:
7775

Status:
Fixed

Date:
2024/03/09

The Fix for Report ID 7745 Causes Sorting Problems, especially When Using Column Formats

Trying to prevent null sorts stops effective sorting techniques, especially when using certain column formats. My bread and butter sort was for Best Time | Transit Time| Altitude [Ascending or Descending would be situational] with Best Time at every 15 minutes and Transit Time at every 5 minutes. To see if these changes would affect my sorting I set both Best Time and Transit Time to Actual Time and looked at the results. I determined that this will really take away from my ability to order things like I used to. I attached a print screen to help illustrate.

Steps to Illustrate:
1. Open the attached document and make sure it is set to February 10th, 2024 with one of the EM... sites.
2. Set it to Civil Twilight End.
3. Sort by Best Time (no options available after that)
*Note that Best Time still uses a format of every 15 minutes for some reason.
*When you go to the objects at 7:30pm for Best Time, It does not automatically sort the Transit column after the Best Time column. It goes from 1:34pm, to 5:53pm and then to 4:48pm. Also, in the 7:30 Best Time range there is one object that transits at 4:53 and another at 4:52. I would normally want to use the 5 minute format to keep both of those right next to each other but they now have 2 objects between them. Even if it did keep them together, I now have no control to say that I want to sort those two by altitude with either Ascending or Descending. If you really look at it, I don't think there are really very many "null" sorts for people who want to be more granular with their sorting.

Attachment: Tagged Columns.PNGAttachment: AstroPlannerV2-W321.prefsAttachment: Main Objects1.apd

Analysis:
I guess the particular case of Best Time (being in 15 minute increments for performance reasons) is an "anomaly" here. I can take the approach of either (a) making Best Time a "non-continuous" or "discrete" value field (easy), or (b) adding Yet More Options to time fields to round them to the nearest n minutes and making those fields discrete values.
(a) is easy. (b) requires extensive surgery and UI changes. Hence, at this stage, I'm going to implement (a).

Resolution:
Fixed.

ID:
7779

Status:
Fixed

Date:
2024/03/08

After upgrading to 2.4b27, User-Defined Fields are Causing Crashes

It is giving me a RunTime Error, with no bug report available, and crashing when going to edit a User-Defined Field. Many times it crashes right when I click on it. Sometimes, it does so after trying to append info to it.

Steps to Duplicate:
1. Open the attached document.
2. Select "Crab Nebula, Taurus A" around the middle of the association.
3. Drag the user-defined Fields pane to the left for more room, if necessary.
4. Click the Description field. If you don't get the error yet then try appending text to the information.
*It should give a RunTime Error (See screenshot).

5. Click OK and the program will kick you out.

Attachment: AstroPlannerV2-W32.prefsAttachment: 2024-01-30 Current List.apdAttachment: RunTime Err wih UDFs.PNG

Resolution:
Fixed. Not sure why this happened, but taking a slightly different approach seems to have fixed the issue.

ID:
7791

Status:
Implemented

Date:
2024/03/03

RA/Dec JNow coordinates

Add (optional) RA/Dec coordinates for Epoch JNow to the object list

Resolution:
Implemented.

ID:
7784

Status:
Fixed

Date:
2024/02/27

Issues with Syncing

I have two computers an M3 MacBook Pro laptop and an M1 Mac mini. In astroplanner I have enable syncing and sync via iCloud. I have also made sure preferences was selected in "items to sync" as well as both computers are pointed to the same path directories. My issue is that I have set up my devises/scopes and location on my laptop and I don't see that data syncing to my Mac mini.

Analysis:
Syncing needs some work, it would seem.

Resolution:
Fixed. Syncing should now work more consistently. Bonus: Added feature to Setup Wizard to allow setting up files from a previously synced AstroPlanner application run.

ID:
7814

Status:
Fixed

Date:
2024/02/22

GraphicsExtensions.PolygonToGraphicsPath: Out Of Bounds Exception

Exception Type: Out Of Bounds Exception

1: Function GraphicsExtensions.PolygonToGraphicsPath( Pair() ) as GraphicsPath
2: Sub GraphicsExtensions.FillPath( extends Graphics, Pair(), boolean )
3: Sub SkyChart.DrawMoon()
4: Function SkyChart.MakeChart() as Picture
5: Function SkyChart.Image.Get( int32 ) as Picture
6: Sub SkyComputeThread.Event_Run()
7: Sub APThread.Event_Run()


User descriptions of above error trace:

a. Was displaying SkyView with several dozen objects and incrementing time one hour.

b. I have now tried several different plans. When I select an item and then click on SkyView, I get this error. Thiw was workoing. Not sure what option (of several) that I changed over the last couple of days that made this stop working, but now Sky view is impossible to use. Each time I utilize it, the app crashes.

c. In the Sky View tab, set the time to 22 hours in the Date/Time widget, and this exception popped up.


User description of above error trace:

I switched from objects to sky view. That's it...


User description of above error trace:

I select any plan file, select Sky view, and the exception pops up. I have tried with several plans; it seems to be a global problem.


User description of above error trace:

In the Sky tab, I changed the time (specifically hours, from 22 to 4) and this exception popped up.


Analysis:
Oops. A bit of code ended up in the wrong place in a recent refactoring. Happens if the date is that of a full moon or new moon.

Resolution:
Fixed.

ID:
7778

Status:
Fixed

Date:
2024/02/12

Selected objects displayed even when set to not display

In the Sky Chart, with the option Objects under Plan Objects selected (tickmarked) and set to Highlighted, both highlighter objects (in the list of objects in the Objects tab) and objects selected in the list of objects are displayed, instead of only highlighted objects.


Analysis:
Actually this is correct - if the selected objects are also highlighted. However they will be displayed in the "selected" colour.

Resolution:
Fixed. Under the conditions described, selected and highlighted objects will be displayed in the same colour.

ID:
7774

Status:
Implemented

Date:
2024/02/09

Update the SDSS image download to use DR18

The current version of the application accesses an older release of SDSS image data (DR7). Update this to use the latest release (currently DR18).

Resolution:
Implemented. The change is implemented. No code changes required. Next time you run AstroPlanner you should see DR18 image data.

ID:
7772

Status:
Fixed

Date:
2024/02/08

Unable to download catalogues

When attempting to download a large catalogue the download aborts with the message "Error: Timeout trying to download inventory!".

Analysis:
Workaround: After opening the Catalogue Manager, wait about 30 seconds for the timeout error to occur. Then try downloading the catalogue.

Resolution:
Fixed.

Show all beta release notes for the current version