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/04/21 10:39 (Pacific time)

Download

VersionRelease DateExpiry Date
2.4b272024/02/04120 days from Release Date

Macintosh

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

Windows

32-bit Application (.exe)Download91.9MiB32-bit version. Installer. Windows 8.1 or later
32-bit Application (.exe.zip)Download91.4MiB32-bit version. Zipped installer
64-bit Application (.exe)Download87.7MiB64-bit version. Installer. Windows 8.1 or later
64-bit Application (.exe.zip)Download87.2MiB64-bit version. Zipped installer
64-bit Application (.exe.zip)Download143.6MiBSpecial 64-bit version for Windows 7 SP1 through 8.0.
32-bit Application (.exe.zip)Download153MiBSpecial 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.4b28
Release Date: Soon
Fixes: 14, Enhancements: 3

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:
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:
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:
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:
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:
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:
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:
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:
7797

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.


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.

Version: 2.4b27
Release Date: 2024/02/04
Fixes: 27, Enhancements: 1

ID:
7766

Status:
Fixed

Date:
2024/02/04

Observation missing

I am trying to enter old observations. When I enter the first observation, all looks well, when I enter the second observation on a second object, its OK, but when I enter the third observation on a third object, the first will no longer display in the log, although the log indicates that there are three observations.

If I then delete the second and third observations that do appear, the first appears. The observation count always stays accurate.

Any idea of what may be happening?

Analysis:
This is a nasty one. The issue is with observations with the same date/time not being shown in the observation database window.

Resolution:
Fixed. All observations should now be displayed. Any missing observations probably don't have a suitable session associated with them. The Observation > Observation Preferences > Rebuild Sessions... feature will fix this.

ID:
7768

Status:
Fixed

Date:
2024/02/04

Hilighting does not update properly with time change

Highlight selection is set to "Visible."

In the Objects window, when changing the Time in the Date/Time widget, the highlighting immediately changes only in the Azimuth and Altitude columns. This is shown in the attached screenshot which was taken immediately after changing the Time from PM to AM.

The highlighting is updated appropriately (i.e. across the whole row) once the window is scrolled.

macOS Ventura 13.6.4 on an M2 MacBook Air. AP version 2.4b26 (ARM).

Resolution:
Fixed. The update should be a lot faster, especially with plan docs with a lot of objects.

ID:
7769

Status:
Fixed

Date:
2024/02/04

Observation database window issue

The observations list does not remember its column width settings.

Resolution:
Fixed.

ID:
7762

Status:
Fixed

Date:
2024/02/02

AstroPlanner Hangs Editing User-Defined Fields

I have AP hanging in multiple documents when trying to edit a variety of text fields.

Steps to Duplicate:
1. Open the attached plan document.
2. Go to the Crab Nebula object and click in the Conditions UDef field. It should select the whole value.
3. Try to type the following text and the program will hang:

NM | NO | NT | PH | Alt>32

Resolution:
Fixed. Well, it no longer hangs. However, you might need to click twice to edit a field. Making it completely right will require major surgery.

ID:
7765

Status:
Fixed

Date:
2024/02/01

CatalogueConstants.GetShortTypeName: Nil Object Exception

Exception Type: Nil Object Exception

1: Function CatalogueConstants.GetShortTypeName( int64, color, gueConstants.CatalogueObjectType()() ) as string
2: Sub TypeSelectPopup.Event_GetMenuItems( byref string() )
3: Sub SelfLoadingPopup.Event_MouseEnter()
4: Sub DesktopPictureButton.Event_MouseEnter()
5: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

I had started AP but was using other applications such email. My mouse moved across AP's window and a Nil object dialog popped up. I don't think I clicked, just moved the mouse over.

Resolution:
Fixed.

ID:
7764

Status:
Fixed

Date:
2024/01/31

Issues with scripting

Several issues with using the TCPSocket framework class. Also, it is possible to start the script running again before the previous instance has completed, causing hard crashes.

Resolution:
Fixed.

ID:
7757

Status:
Fixed

Date:
2024/01/29

ShortTermVisibilityCanvas.DrawShortTermVisibility: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub ShortTermVisibilityCanvas.DrawShortTermVisibility( Graphics )
2: Sub ShortTermVisibilityCanvas.Event_Paint( Graphics, Xojo.Rect() )


User description of above error trace:

Just installed this version(beta 2.4b26) after removing the previous non-beta version and installing this beta version.


Resolution:
Fixed.

ID:
7716

Status:
Fixed

Date:
2024/01/29

Entering new observations - values of user fields

When entering subsequent observations, values for user fields (in my case: limiting magnitude, seeing, SQM and temperature) for a new observation are copied from an observation logged at a later time and already present in the observation database. The desired functionality would be to have the values copies from the preceding observation.

This is probably a bug, but it would only manifest itself if a sessions already contained (an) observation(s) logged at a later time.


Resolution:
Fixed.

ID:
7728

Status:
Fixed

Date:
2024/01/29

ShortTermVisibilityCanvas.DrawShortTermVisibility: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub ShortTermVisibilityCanvas.DrawShortTermVisibility( Graphics )
2: Sub ShortTermVisibilityCanvas.Event_Paint( Graphics, Xojo.Rect() )
3: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Reference bug report 7721. The first opening of any plan file now gives this error.


User description of above error trace:

Reference bug report 7721. I have just reported an error that occurs when any plan is opened. This error then occurs when the location is changed. Astroplanner then give a message requiring that it close.


Resolution:
Fixed.

ID:
7763

Status:
Fixed

Date:
2024/01/28

Solar System Object Motion

The Solar System Object Motion shows a mark of the asteroids position but does not show the magnitude or time information. I tried checking them on and off individually but still the information does not appear in the FOV.

Analysis:
Oops. I screwed up some refactoring I did a year or so ago.

Resolution:
Fixed.

ID:
7758

Status:
Fixed

Date:
2024/01/26

Highlighting rule file loading issue

If you import a custom highlighting definition file containing rules on user-defined fields, and the plan does not have such a user-defined field then weird stuff happens.

Analysis:
The current rules file format is not designed to handle user-defined fields very well. As a bonus, it also doesn't handle rule files saved with a newer version of the app if that app has new built-in fields and there's a rule active on that field.

Resolution:
Fixed. The rules file is now a completely different format. If anomalies are found when loading, they are reported to the user. Note that you can still load old format files, but you will be warned that there might be issues if you proceed.

ID:
7734

Status:
Fixed

Date:
2024/01/24

Eagle Nebula [1] incorrect in Guides

Steps to Duplicate:

Not certain if this is fixed so sorry I am still on the older version. My highlight rules didn't convert right somewhere earlier on and I want to fix them before upgrading.

1. Go to New Object and pop down Guides. In Common deep-sky objects..., there are two Eagle Nebula choices.
Choose the first one and it actually chooses the ID for Seagull Nebula, which is IC2177.
2. Backspace over the incorrect choice and then choose the second Eagle Nebula choice.
*It's shows nothing so you can't double choose (not sure if that's considered a problem).
3. Choose Cancel.
4. Now repeat step 1 but choose the second Eagle Nebula choice. Now it works and this one is correct.

I like the idea of two choices with the first one being M16 instead of Seagull, since the second choice is a cluster type and M16 includes the Nebula.


Analysis:
See #7736.

Resolution:
Fixed. Apart from issues resolved by #7736, the info about the common DSO objects (and stars) is displayed below the popup for added verification purposes.

ID:
7740

Status:
Fixed

Date:
2024/01/24

Custom Colors Overwrite Each Other in Highlight Rules

When trying to add a second custom color to the pallette, it overwrites the first one.

Steps to Duplicate:
1. Open the attached document.
2. Choose the Highlight dropdown on the Site widget and select Edit Custom Highlighting.
3. Select the rule called "Site Observability: No DT, Dark Site Object, Too Low Currently, Past Mag Limit"
4. Choose Rule Set#2 and click the blue text color. Click Define Custom colors and the current shade will be shown.
5. Adust the picker up to make the color a little lighter and then click Add to Custom Colors.
*It will now be the upper left-most color because I want to swap colors with Rule#1. Click OK.
6. Choose Rule Set#1 and repeat Step 4 for this rule.
7. Repeat step 5 and notice that the new custom yellow color has overwritten the blue color in the upper-left position.

I am not sure if I am doing something wrong but I was expecting it to take the next spot for a custom color, not to overwrite the previous one.

Attachment: Main Objects.apd

Resolution:
Fixed.

ID:
7736

Status:
Fixed

Date:
2024/01/24

Lobster Nebula Confusion

NGC 6357 has only 2 nicknames, the main one probably being Lobster Nebula. NGC 6618 has many names, the most popular seeming to be Omega Nebula or Swan Nebula, but also including Lobster Nebula. Both of them are named Lobster Nebula in the Guides drop-down, causing some confusion as to which one goes where.

Steps to Duplicate:
1. Go to New Object and pop down Guides. In Common deep-sky objects..., there are two Lobster Nebula choices. The choice for Swan Nebula and Omega Nebula also are listed.
2. Choose the first Lobster Nebula and it chooses the ID NGC 6618.
2. Choose Cancel.
3. Now repeat step 1 but choose the second Lobster Nebula choice. This one is for NGC 6357.

I think it would be good to somehow clarify any objects, which are actually different, but that can share the same nickname. Maybe a Constellation indicator in perins or something.


Resolution:
Fixed. Popup entries now contain ID (where applicable) and constellation. e.g.
Lobster Nebula [NGC6618, SerCauda]
Lobster Nebula [NGC6357, Sco]

ID:
7754

Status:
Fixed

Date:
2024/01/23

Adding Minor object corrupts another object

If I add a Minor Planet... using the Add Special button then another object in the plan will have its type changed to Minor and its coordinates set to an object below the horizon.

I added M33 to the plan that was currently above the horizon (34 degrees). I then clicked Add Special->Minor Planet... and selected (4) Vesta from the MPC list. Vesta is added but M33's type is changed to minor and the coordinates of M33 are now well below the horizon (-61 degrees).

Please find attached a screenshot of the M33 entry and then what happens when (4) Vesta is added.

Attachment: Screenshot 2024-01-21 222434.pngAttachment: Screenshot 2024-01-21 222604.png

Resolution:
Fixed.

ID:
7730

Status:
Fixed

Date:
2024/01/23

Highlighting rules do not work.

I updated from the pre 26 beta to the new b26 and the highlighting rules behaviour has changed. Even though rules are not being satisfied they are being highlighted with the rules colour. The problem appears to happen when more than one rule has been specified.

I added a rule to highlight in green when Observability is greater than 50 and another rule to highlight in orange when observability is between 30 and 50. The observability column for the two objects in the plan was 45.2 and 42.2 but they are still highlighted green. Removing the second rule removes the green highlighting. I even managed at one point to get striped green/orange highlighting when the observability of both objects was in the 40s.

Resolution:
Fixed.

ID:
7755

Status:
Fixed

Date:
2024/01/22

Supernova with SN type

I imported a supernova from ASRAS, 2024gy. Its Type was SN. On the Field of View tab the supernova was not shown. If I changed the type in the Object editor to Supernova then it appeared. In fact changing the type to random names (Fred, BigBaddaBoom) made it appear in the FOV tab. I also tried adding SN as a User-defined type on the Field of View Preferences but it still did not appear. Not sure why the default SN type does not appear on the FOV tab.

Resolution:
Fixed.

ID:
7752

Status:
Fixed

Date:
2024/01/20

NexStarMount.GetItem: Out Of Bounds Exception

Exception Type: Out Of Bounds Exception

1: Sub NexStarMount.GetItem( oi8A1v )
2: Sub TelescopeMount.Get( paramarray oi8A1v )
3: Sub CompareCTDialog.FetchValue( CompareCTDialog, int64 )
4: Sub CompareCTDialog.CompareCTThread_Run( CompareCTDialog, APThread )
5: Sub APThread.Event_Run()


Resolution:
Fixed.

ID:
7738

Status:
Fixed

Date:
2024/01/20

PlanObsAttachment.Path.Set: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub PlanObsAttachment.Path.Set( int32, FolderItem )
2: Sub ObsFilesContainer.ChangeListEntry( ObsFilesContainer )
3: Sub ObsFilesContainer.UpdateTimer_Action( ObsFilesContainer, Timer )
4: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Working with observations


Resolution:
Fixed.

ID:
7749

Status:
Fixed

Date:
2024/01/20

Utility.ReadBOM: I/O Exception

Exception Type: I/O Exception
Exception Number: 89

1: Sub TextInputStream.CheckForError()
2: Function TextInputStream.ReadLine( TextEncoding ) as string
3: Function Utility.ReadBOM( TextInputStream, int64 ) as string
4: Function Utility.ReadBOMLine( extends TextInputStream ) as string
5: Function App.OpenFileFromDisk( FolderItem, boolean, int64, int64, int64, int64 ) as MainWindow
6: Function App._FileOpen_Action() as boolean
7: Sub DesktopApplication._CallFunctionWithExceptionHandling()


number=89


Resolution:
Fixed.

ID:
7741

Status:
Fixed

Date:
2024/01/20

BackupItem.FilePath: Out Of Bounds Exception

Exception Type: Out Of Bounds Exception

1: Function BackupItem.FilePath( int64 ) as FolderItem
2: Sub RestoreDialog.SetupList( RestoreDialog )
3: Function RestoreDialog.SetArchives( RestoreDialog, FolderItem() ) as boolean
4: Function App._BackupRestoreRestore_Action() as boolean
5: Sub DesktopApplication._CallFunctionWithExceptionHandling()


Resolution:
Fixed.

ID:
7751

Status:
Fixed

Date:
2024/01/19

Rise/Transit/Set not recomputed when Site changes

I just noticed that the Rise/Transit/Set values in a plan document do not change if the Site is changed.

Resolution:
Fixed.

ID:
7750

Status:
Fixed

Date:
2024/01/19

Always Save Changes issue

If I close the plan or exit AstroPlanner, I get the Save Changes dialog again even though I selected Always Save Changes previously.

Resolution:
Fixed.

ID:
7745

Status:
Fixed

Date:
2024/01/16

Sort List issue

Using the Sort List popup allows you to sort the list by up to three fields. This can provide bogus or null sorts if you sort any field after sorting a "continuous" value field, since there is a very small chance that the first field will be equal for two objects. e.g. if you sort by RA, and then Dec, it's unlikely that two objects will have exactly the same RA value, so the second (Dec) value is never used. However, if you sort by a field with "discrete" values, e.g. constellation, type, etc., then it is valid to add a second field (e.g. magnitude). The Sort List dialog should not allow "bogus" sorts.

Resolution:
Fixed. The Sort List dialog will now disable further sub-sorting if a "continuous" value field is selected.

ID:
7746

Status:
Fixed

Date:
2024/01/16

TypeDisplaySelector.!GetSymbol( string ) as int64: Out Of Bounds Exception

Version: 2.4b26
Expires: 27/04/24
Date: 17/01/24 9:04:27 am NZDT
OS: Windows 11.0.22621 (X86)

Exception Type: Out Of Bounds Exception

1: Function TypeDisplaySelector.!GetSymbol( string ) as int64
2: Sub FoVChart.MakeObjectCatalogueFind( PlanObject, CatalogueFind(), boolean )
3: Function FoVChart.GetNonSolarSystemPlanObjects() as CatalogueFind()
4: Sub FoVChart.GetInternalCatalogueObjects()
5: Sub FoVChart.ExtractObjects()
6: Sub FoVComputeThread.Event_Run()
7: Sub APThread.Event_Run()

Resolution:
Fixed. Not sure what the issue is/was, but I have added some code to try and avoid it in future.

ID:
7737

Status:
Implemented

Date:
2024/01/04

Improvements to Comet/Minor Planet import

a. Fixed an issue that greatly improves initial import time for objects, especially for large databases such as MPCORB.

b. Added a Settings... button for each data source that lets you choose a convenient subset of the imported data (e.g. first 1000 objects, last 10000 objects, etc.) to improve loading time for data.

c. Some minor cosmetic improvements.

Resolution:
Implemented.

ID:
7735

Status:
Fixed

Date:
2024/01/03

Import comet data

Importing comets for the first time is working fine.
But afterwards the comet cache file must be deleted manually (C:UsersusernameAppDataRoamingAstroPlannerCaches).
If not, an exception error will occur.
When trying to exit without sending an email the program disappears from the screen but the process is not closed (forced via Task Manager -Windows 11).
Sometimes the program stays visible and cannot be closed the normal way.
Right clicking the "Use cached" to delete the cache file doesn't work.

Analysis:
The cache file is being left open, which means access the second time causes an exception. For both comets and minor planets/asteroids

Resolution:
Fixed.

ID:
7733

Status:
Fixed

Date:
2024/01/03

SolarSystemObjectCollection.DeleteCacheFile: I/O Exception

Exception Type: I/O Exception
Exception Message: File is currently in use
Exception Number: 104

1: Sub FolderItem._RaiseIOErrorAsNeeded()
2: Sub FolderItem.Remove()
3: Sub SolarSystemObjectCollection.DeleteCacheFile()
4: Function SelectSolarSystemCollectionDialog.UseCached_ContextualMenuItemSelected( SelectSolarSystemCollectionDialog, DesktopCheckBox, DesktopMenuItem ) as boolean
5: Sub DesktopWindow.ShowModal( DesktopWindow )
6: Function SolarSystemObjectCollection.GetCollectionToDownload( byref boolean ) as SolarSystemObjectCollection
7: Function CometObjectCollection.GetCollectionToDownload( byref boolean ) as SolarSystemObjectCollection
8: Sub SolarSystemObjectCollection.StartImport( MainWindow )
9: Function MainWindow._NewImportCometData_Action( MainWindow ) as boolean
10: Sub DesktopApplication._CallFunctionWithExceptionHandling()


User description of above error trace:

Wanted to erase Comet cache by right clicking using the IAU Minor Planet Center
number=104
message=File is currently in use


Resolution:
Fixed.

Show all beta release notes for the current version