AstroPlanner Beta Testing

ID:
8186

Status:
Fixed

Date:
2026/10/10

After the latest update, searching with the Any ID doesn't select the object

This can be duplicated by searching on the name of GDC1646

Steps to duplicate:
1. Go to Show Catalog> Galactic Dust Cloud Catalogue
2. Choose Any for the ID type and put in BDN99.01+4.01.
It stops searching right away with no errors. However, nothing seems to happen. If you scroll down to GDC1646 then it is not selected.

Attachment: AstroPlannerV2-W321.prefsAttachment: Inventory.txt

Resolution:
Fixed.

ID:
8189

Status:
Fixed

Date:
2026/10/10

Searching for an ID in the HD catalog selects everything

Steps to duplicate:
1. Click the Show Catalogue widget. Choose Henry Draper Catalogue
2. In the Find field for the ID choose "HD", type 242909 for the search value.
*It stops searching with no chime. However all rows are selected, even when scrolling down.

Resolution:
Fixed.

ID:
8196

Status:
Fixed

Date:
2026/10/10

Highlight rules in the Observation category are enabled for unobserved objects.

Maybe I am not understanding how this should work, but both the object and observation rules for Found will highlight objects that have no observations at all if set to False. Other Observation rules, which don't have a sister under Objects, do the same thing. I would expect the Observation rules to only affect objects that have one or more actual observations.

Steps to duplicate:

1. Have a plan document open with at least one object that has never been observed and at least one object that has been observed but has never been found in an observation.
2. Go to Object> Highlight> Edit Custom Highlighting.. and click the widget to start a rule.
3. Clear out any current settings from Rule Set #1, Rule Set #2, and Rule Set #3.
4. For Rule Set #1, enable the ObjectFound rule and set it to False
5. For Rule Set #2, enable the ObservationFound rule and set it to False. Make sure it is for All Observations. Click OK.
6. For Rule Set #3, enable the ObservationSessionSites rule and set to Does not Contain: All of. For the values give it a filter which includes all sites that the observed object has been observed at.
*Both the never observed object and the object that has never been found in an observation are highlighted by all three rule sets.
It is my understanding that Rule Set #1 should highlight both objects but Rule Sets #2 and #3 should only highlight the object that had actually been observed and not found. Otherwise, I cannot see a reason for the two different found settings. Also, I would reasonably assume you'd only want to have the Telescope rule for objects that have observation(s) and there would be no reason for it to highlight non-observed objects. It's true that I could use ObjectObservations are: greater than 0 for Rule Set #3. However, for Rule Set #2, I wanted to have objects highlighted that Either were not found in an observation OR used certain low magnification optics (via the Telescope rule). I cannot do this if I have to add in Observations are greater than 0 because then I'd have to require all rules to be true.

Resolution:
Fixed. If either (a) a rule set contains any observation rules but the object has no observations, or (b) a rule set includes an object.Found rule and the object has no observations, then the ruleset always returns false (and no highlighting is done) regardless of any other rules.

ID:
8176

Status:
Fixed

Date:
2026/09/07

Lookup Name doesn't find objects that searching Name Contains does in Search Catalogue/s

Maybe I just do not understand this feature but I could not tell in the User Manual from the Lookup Name section.

Steps to duplicate:
1. Go to the Search Catalogue/s widget and choose the Star Clusters in the Milky Way catalog.
2. Uncheck all the options except for Name Contains. Type in CepOB2A
3. Click Search and it returns APOC3087
4. Cancel out of the Search Results dialog.
5. Go to the Lookup widget and choose Name.
6. Type CepOB2A and click OK.
7. Choose None and then select the box for Star Clusters in the Milky Way catalog
8. Click OK.
*Nothing is found.

Attachment: AstroPlannerV2-W32.prefs

Analysis:
It appears that the Lookup feature is searching on ID even if you choose Name as the field to search. Looking at the code, it would seem the feature assumes the Name field contains one or more comma-separated IDs, and you want to search for those IDs

Resolution:
Fixed. The Lookup feature popup menu contents are now more closely ties to what is or isn't selected in the object list.

ID:
8175

Status:
Fixed

Date:
2026/09/07

Searching on an the Any ID in Show Catalogues does nothing anymore

If you put a valid ID number it either does nothing in the catalogue or it chimes and still does nothing. In the past, it has found the text in Name, and maybe Description, before. I would think it would find an ID number, for any catalogue column, as well but I can't make that happen either. There is also nothing in the documentation that says exactly what searching Any is supposed to do.

Steps to duplicate:
1. In a plan document, click the Show Catalogue widget and choose the Galactic Dust Cloud catalog.
2. For Find, choose Any and type in BDN99.01+4.01.
*It will eventually chime and show nothing.
3. Change Find to GDC and type 1646.
*It will do the same thing.
4. Close the catalog and then reopen it using step 1. It will be set to GDC for Find.
5. Now type 1646.
*It will find this GDC object with BDN99.01+4.01 in the name (This used to work for Any). Now Any seems to stop subsequent searches until you reopen.
6. Close this catalogue and repeat step 1 for the STAR Asterism catalogue.
*This is a fairly small, clean catalogue. Nothing has a name with contains the string 22 but there is an object with ID 22.
7. Change Find to Any and type 22.
*It chimes and doesn't do anything.

Attachment: AstroPlannerV2-W321.prefs

Analysis:
One issue (in this case) is that the Name field is not included in the search when Any is selected - only the ID fields. This can be rectified.

Another issue is searching on partial ID/Name information (e.g. 22). Unfortunately this would require major surgery which I'm not going to perform for V2.4.1. Please add a feature request for this.

The other issue is the failure of "Any" search after the first one. Under investigation. Difficult to reproduce. It is possible that solving the first issue above has resolved this one.

Resolution:
Fixed (partially). "Any" search now also searches Name and Description fields (if present). Note that (currently) the search term will only match if is at the start of those fields.

ID:
8150

Status:
Fixed

Date:
2026/09/07

Even after upgrading, the DSH catalog cannot be searched.

Steps to duplicate:

1. Go to File> Catalogue Manager> Coverage and Settings. Select Deep Sky Hunters Catalogue and make sure "Don't Search" is not checked. Exit out.
2. Go to New Object and type in DSHJ1817.1-1842, then click All. No object was found and it asks for an exhaustive search.
3. Say Cancel to the exhaustive search and close Search Results.
4. Click Show Catalogue and choose the Deep Sky Hunters Catalogue.
5. In the Find field, type in J1817.1-1842 for DSH. After a time it chimes and can't find the object.
6. Scroll down to find the object and choose to Add Selected. This confirms the catalog has the item.

Attachment: AstroPlannerV2-W32.prefs

Analysis:
Because "DSHJ1817.1-1842" is parsed as "DSHJ" + "1817.1-1842", it can't find a catalogue with the "DSHJ" ID. This will need to be considered a special case in the application and handled as such.

Resolution:
Fixed.

ID:
8179

Status:
Fixed

Date:
2026/09/06

Catalogues checked under By Name are not checked under By Type but their outlines still show.

This causes confusion, especially when you are going back and forth with adjustments. In the last situation for me, it took me about 25 minutes before I decided to go look under By Name.

Steps to duplicate:

1. Open the attached document while using my resources file. Select the Flying Minnow object with an ID of STAR4.
2. Go to the Field of View tab.
3. It should be on By Type. Make sure the Advanced VX SCT 8" scope is chosen with a 40mm eyepiece.
4. Choose By Type. Check a catalog in some category but not the SAC DSO catalog.
5. Let's say you wanted to adjust the size of something or check it's properties. Go back to the objects tab.
6. Go back to the FoV tab.
7. Click into Field Diameter and change it to 1°33'18.0".
*Notice there should now be a white outline in the NE.
8. Expand Clusters and go to Open Clusters. Try unchecking catalogs but it won't help to get rid of the white outline (don't so anything with SAC DSO).
9. Switch to By Name.
10. Uncheck SAC DSO and the outline will disappear.

Attachment: AstroPlannerV2-W32.prefsAttachment: AstroPlanner ResourcesAttachment: 2025-04-18 Candidates (Current).apd

Resolution:
Fixed.

ID:
8182

Status:
Fixed

Date:
2026/09/06

Some stars in FoV are using, what appears to be, minor planet symbols

These symbols are taking up unnecessary space and are kind of clumsy.

Steps to duplicate:
1. Open the attached document with the attached resource and preference files loaded.
2. Select the object for Pleiades, Seven Sisters.
3. Go into the Field of View tab. Select the Advanced VX 8" SCT telescope and Explore Scientific 40mm eyepiece.
4. Changed Field Diameter to 2°13'18.0". In Display Options, choose Legend under Other.
5. Select All-Sky Compiled under catalogs. One of the stars will now show a Minor Planet symbol.
6. Select APASS (DR9) North as a catalog.
*Now many small magnitude stars will show the Minor Planet symbol as well.
7. Uncheck APASS (DR9) North and choose Hubble Guide Star.
*This now shows many small magnitude stars as small dots without the Minor Planet symbols. So this seems to be related to catalogs somehow.

Attachment: AstroPlannerV2-W32.prefsAttachment: AstroPlanner ResourcesAttachment: Inventory.txtAttachment: 2020-02-20 Test of Celestron SkyPortal and User Objects.apd

Analysis:
Actually it's similar to the minor planet symbol, but has a dot in the middle. This represents a catalogue star with no given magnitude. However this is (a) confusing, and (b) the symbol doesn't appear in the legend.

Resolution:
Fixed. Changed the symbol for a star with no magnitude to a simple "x", and also added it to the legend popup window.

ID:
8178

Status:
Fixed

Date:
2026/09/06

SACAst Asterisms not showing in FoV at all

For some reasons, any asterisms from this catalog will not show up in Field of View.

Steps to duplicate:
1. Open the attached document.
2. Select the item called Crown Cluster and go to Field of View.
3. Make sure the STAR, DSH, SAC Asterism, and Star Clusters in the Milky Way catalogs are selected with the scope of By Name.
4. Set the telescope to AVX 8" SCT. Set the eyepiece to 32mm.
5. Hover the mouse in the area between STAR19 and APOC4376. Right-Click and choose "Lookup synonyms of STAR 19..."
*SacAst 46 is an option in the Synonyms Search Results dialog. However, it does not show up anywhere in FoV if you close the Synonyms Search Results dialog box.
6. Go back to the Objects tab.
7. Select the object with the SACAst20 ID. Go to the Field of View tab. Set the eyepiece to 40mm and then change the degree in Field Diameter from 1 to 2.
*There is no label for SACAst20, nor any outline for it. However, there are outlines for its synonyms from STAR, DSH, and APOC.

Attachment: AstroPlannerV2-W32.prefsAttachment: AstroPlanner ResourcesAttachment: 2025-04-18 Candidates (Current).apd

Resolution:
Fixed. Added Asterism graphics to FoV and legend.

ID:
8166

Status:
Fixed

Date:
2026/09/06

Size appears with 7 decimals in objects added to a plan

To reproduce: create a new plan and add NGC1316. The NGC catalog says its size is 7,1, but in the plan it appears as 7.0999999. Similarly, NGC1232 size shows as 7.8000002 instead of 7,8, and so on.

All my plans use commas as decimal separators in all columns, except in this case, that uses points. I have added new objets to an old plan, and the size appears as x,x for old objects and x.xxxxxxx for the new ones.

Resolution:
Fixed.

ID:
8147

Status:
Fixed

Date:
2026/09/06

Incorrect transit dates

Transit dates are incorrectly calculated/displayed. Attached is a plan (AL double star club) and two screen shots. The screen shots show (1) a view of the plan with transit dates showing, and (2) the “Edit Object List Columns”, with the time for the transit date calculation showing. The highlighted object - N Hydrae - transits at 12:00 AM on 4/23, not 7/19.

Resolution:
Fixed.

ID:
8183

Status:
Fixed

Date:
2026/09/05

SN_GRB_Functionality.DoGRBImport: XMLException

Exception Type: XMLException
Exception Message: msg:XML parser error 7: mismatched tag
Exception Number: 2

1: Sub XMLDocument.Constructor( FolderItem )
2: Sub SN_GRB_Functionality.DoGRBImport( FolderItem, string )
3: Sub SN_GRB_Functionality.SelectGRB()
4: Function MainWindow._ImportGRBData_Action( MainWindow ) as boolean
5: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

Trying to import GRB DATA
number=2
message=msg:XML parser error 7: mismatched tag

Analysis:
Unfortunately, the on-line GRB data source has gone away and I can't find a suitable up-to-date replacement.

Resolution:
Fixed. Removed the Import > Gamma Ray Burst Data option. Sorry.

ID:
8157

Status:
Implemented

Date:
2026/07/17

Support PiFinder export

Support object export to a text file for uploading to a PiFinder device.

Resolution:
Implemented.

ID:
8148

Status:
Implemented

Date:
2026/07/05

All-Sky Coverage Map enhancement

I have a proposal for a future version of the All-Sky Coverage map.

I find the map very interesting, but for practical purposes, such as determining whether an object is close to the telescope or needs to flip its meridian, it doesn't provide any help.

I'd like the map to show the currently selected object in a different color, and if the telescope is connected, its approximate position in the sky.

Resolution:
Implemented. Selected object/s now show in red with an outside red ring. Telescope pointing (where selected and applicable) shows as a larger purple ring with cross-hairs.

Bonus:
- There's now an option to draw the (0° altitude) horizon line on the chart.
- There's now an option to draw the meridian line on the chart.

ID:
8146

Status:
Fixed

Date:
2026/07/04

ScrollingImageCanvas.AnnotatePicture: ThreadAccessingUIException

Exception Type: ThreadAccessingUIException
Exception Message: A thread has attempted to manipulate a user interface element. This can only be done from the application's main thread.

1: Function DesktopListBox.RowCount.Get( int32 ) as int64
2: Function MainWindow.GetObjectIDFromList( MainWindow, double, double ) as string
3: Function MainWindow.!GetObjectID( double, double ) as string
4: Sub ScrollingImageCanvas.AnnotatePicture( ScrollingImageCanvas, Graphics, int64 )
5: Sub ScrollingImageCanvas.LoadImagesThread_Run( ScrollingImageCanvas, Thread )

Resolution:
Fixed.

ID:
8088

Status:
Fixed

Date:
2026/06/17

Image download for all objects - always prompted at app launch

Each time I launch AP, latest beta (but was also true with previous versions), I get prompted to "Download images for all objects in xxxx.apd plan document".
I always check the "Don't show this again" checkbox and select "No".
The checkbox doesn't seem to work.

Analysis:
The Yes/No dialog "Don't show this again" option assumes (if selected) that Yes is always wanted. Unfortunately, this isn't what you want to happen.

There's also a chance (I haven't checked yet) that this is happening before the preferences have been read in, although I doubt it.

Anyway, fixing this issue properly is a bit of a challenge, so I need to think about it more.

Resolution:
Fixed. Well, not really, However, the Yes/No message dialog now tells you how to switch off the option that's causing this (Image > Image Preferences > Automatic image download)

ID:
8086

Status:
Fixed

Date:
2026/06/17

SelectSolarSystemCollectionDialog.CheckButtons: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub SelectSolarSystemCollectionDialog.CheckButtons( SelectSolarSystemCollectionDialog )
2: Sub SelectSolarSystemCollectionDialog.FromFileBtn_Pressed( SelectSolarSystemCollectionDialog, PDPushButton )
3: Sub DesktopWindow.ShowModal( DesktopWindow )
4: Function SolarSystemObjectCollection.GetCollectionToDownload( byref boolean ) as SolarSystemObjectCollection
5: Function MinorPlanetObjectCollection.GetCollectionToDownload( byref boolean ) as SolarSystemObjectCollection
6: Sub SolarSystemObjectCollection.StartImport( MainWindow )
7: Function MainWindow._NewImportMinorPlanetData_Action( MainWindow ) as boolean
8: Sub DesktopApplication._CallFunctionWithExceptionHandling()

Resolution:
Fixed.

ID:
8108

Status:
Fixed

Date:
2026/06/15

Issues refreshing from Catalog

After the latest update, the Objects to Refresh setting is still not holding and the Magnitude setting is actually not being refreshed. This is from an object which has had its ID changed. Steps to duplicate:
1. Open the attached document and select the object named "Kepler 16*"
2. Right click the object and choose Show Object in Catalog (This object is in the APASS North catalog)
*The magnitude of the object is 12.28 but it is currently set to 12.10
3. Go to Object > Refresh from Catalogues... Change "Objects to Refresh" to Selected Objects. Select only Magnitude under Select fields to refresh. Click Ok.
4. The magnitude remains at 12.10.
5. Go back into Object > Refresh from Catalogues.. "Objects to Refresh" has gone back to All Objects.

Analysis:
If the ID of an object being refreshed has been changed after adding it from a catalogue, and that new ID can't be found in the original catalogue, the object will not be refreshed.

Resolution:
Fixed. If the object ID has been changed and can't be found in the original catalogue, you'll now be asked if you'd like to update the object from the original catalogue entry.

(I can't reproduce the "Objects to Refresh setting is still not holding" issue, so I can't fix that)

ID:
8142

Status:
Fixed

Date:
2026/06/06

ASCOM.TrackingRates: Nil Object Exception

Exception Type: Nil Object Exception

1: Function ASCOM.TrackingRates() as M.DriveRates
2: Function ASCOMMount.GetTrackingRates() as untConstants.MountParam
3: Sub ASCOMMount.GetItem( oi8A1v )
4: Sub TelescopePaletteWidget.Initialise( TelescopePaletteWidget )
5: Sub TelescopePaletteWidget.mw.Set( TelescopePaletteWidget, int32, MainWindow )
6: Sub TelescopePaletteWindowWin.mw( TelescopePaletteWindowWin, assigns MainWindow )
7: Sub TelescopeMount.SetItem( oi8A1v )
8: Sub ASCOMMount.SetItem( oi8A1v )
9: Sub TelescopeMount.SetNoLock( paramarray oi8A1v )
10: Function MainWindow._TelescopeTelescopeControlPalette_Action( MainWindow ) as boolean
11: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

Trying to connect to synscan wifi. Ascome driver. Synscan pro is running on iPhone. Connected trough tcp

Resolution:
Fixed. Hopefully.

ID:
7082

Status:
Fixed

Date:
2026/06/06

ASCOM.TrackingRates: Illegal Cast Exception

Exception Type: Illegal Cast Exception
Exception Message: _VariantString cannot be cast to OLEObject

1: Function ASCOM.TrackingRates() as M.DriveRates
2: Function ASCOMMount.GetTrackingRates() as untConstants.MountParam
3: Sub ASCOMMount.GetItem( oi8A1v )
4: Sub TelescopePaletteWidget.Initialise( TelescopePaletteWidget )
5: Sub TelescopePaletteWidget.mw.Set( TelescopePaletteWidget, int32, MainWindow )
6: Sub TelescopePaletteWindowWin.mw( TelescopePaletteWindowWin, assigns MainWindow )
7: Sub TelescopeMount.SetItem( oi8A1v )
8: Sub ASCOMMount.SetItem( oi8A1v )
9: Sub TelescopeMount.SetNoLock( paramarray oi8A1v )
10: Function MainWindow._TelescopeTelescopeControlPalette_Action( MainWindow ) as boolean
11: Sub Application._CallFunctionWithExceptionHandling()

message=_VariantString cannot be cast to OLEObject

Resolution:
Fixed. Hopefully.

ID:
8129

Status:
Fixed

Date:
2026/06/05

"Download images for all objects in the XXX plan document" NO + Don't show this again not honored

When launching the app, the message box mentioned in the bug title always shows up. “The Don’t show this again” checkbox is ignored.

Reproducible 100% of the time.

Analysis:
This because the "Don't show this again" checkbox assumes you will want the Yes option. If you always want the No option then you need to turn off this download feature via Image > Image Preferences > Automatic image download.

Resolution:
Fixed. The dialog now adds info on how to turn off the feature.

ID:
8135

Status:
Fixed

Date:
2026/06/04

Dk Start, Dk Dur and Dk End show "---" for observable object

For several objects the table shows „—-„ even thought the object is observable.

I encountered this behaviour when being on the Southern Hemisphere (location 23° 19' S and 17° 57' E), e.g. for the object M8 on April 19th 2026.
M8 is high up in the sky for most of the night, and the table shows „—„.

When switching the location to Australia, the behaviour looks more reasonable (i.e. then the table is populated with the respectived hours).

Is this a misunderstanding on my side, or a bug?

Analysis:
This is definitely a bug.

Resolution:
Fixed.

ID:
8082

Status:
Fixed

Date:
2026/06/03

Custom Highlighting Won't Load.

When trying to load a saved Custom Highlighting saved file (set.hrules), a bad file format message pops up with "file does not appear to be valid rule set file". This happens with older saved rule sets and new clean default rule sets. Attached is an image of the error and a saved set.hrules file.

Attachment: set.hrulesAttachment: Highlight Load Error.jpg

Resolution:
Fixed.

ID:
8099

Status:
Fixed

Date:
2026/05/28

RestoreDialog.items_MouseMove: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub RestoreDialog.items_MouseMove( RestoreDialog, StripedListBox, int64, int64 )
2: Sub DesktopWindow.ShowModal( DesktopWindow )
3: Function App._BackupRestoreRestore_Action() as boolean
4: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

chanhinh computers

Resolution:
Fixed.

ID:
8090

Status:
Implemented

Date:
2026/05/28

Object Property vs Time feature

I noticed that closing the window and reopening it "forgets" the setting "Selected object: transit time" but always shows the current time.

For me it would be useful to have two arrows in the window to be able to scroll forward/backward through the objects on the plan without having to close the window, right click the mouse, etc. and set "Selected object: transit time" every time.

Analysis:
Changed from a bug to an enhancement.

Resolution:
Implemented. Added buttons to let you move forwards or backwards through the plan objects.

ID:
8133

Status:
Fixed

Date:
2026/05/27

DesktopListBox.SortingColumn.Set: Out Of Bounds Exception

Exception Type: Out Of Bounds Exception

1: Sub DesktopListBox.SortingColumn.Set( int32, int64 )
2: Sub ObjectListbox.SetSortColumn( int64 )
3: Sub MainWindow.OnOpen( MainWindow, FolderItem, boolean )
4: Function App.OpenADocumentFile( FolderItem, byref MainWindow, string, boolean, boolean, int64 ) as boolean
5: Function App.OpenDocuments() as boolean
6: Sub App.Event_Opening()
7: Sub DesktopApplication._CallFunctionWithExceptionHandling()
8: Sub REALbasic._RunFrameworkInitialization()

Resolution:
Fixed.

ID:
8131

Status:
Fixed

Date:
2026/05/27

Observation logged in open session not (always) displayed.

Often, when working out observations, the nr. of observations already logged in the session are not displayed in the Observations tab. A restart of the application will fix this, but it seems to happen again when continuing to use the application again after putting the computer in standby.

Resolution:
Fixed. I hope.