AstroPlanner Beta Testing

ID:
7935

Status:
Fixed

Date:
2025/06/14

Default font (size) in observation database does not stick

When setting a different font size for observation notes in the observation database, the font size does not "stick", but reverts back to its previous setting.

For example, when setting the font size for an observation note to 18, it reverts to 13 once a different object is selected. I think the preferred behavior is to set a font size which is then applied to (and maintained for) all observations in the database.

Attachment: Scherm��afbeelding 2025-04-22 om 13.49.38.jpg

Analysis:
The observation notes, in this case, are read-only, and the Default Font... item should not be present.

Resolution:
Fixed. The Default Font... item is removed from the contextual menu if the field is read-only.

ID:
7934

Status:
Fixed

Date:
2025/06/14

MainWindow.GetFoVRADec: Nil Object Exception

Exception Type: Nil Object Exception

1: Function MainWindow.GetFoVRADec( MainWindow, int64, int64, byref double, byref double ) as boolean
2: Sub MainWindow.CentreFoVOn( MainWindow, int64, int64 )
3: Sub MainWindow.FoV_DoublePressed( MainWindow, CMMCanvas, int64, int64 )
4: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

1. Double clicked the FoV to center a position and this exception popped up.

2. Double clicked a position in the FoV, to center it, and this exception popped up.

Resolution:
Fixed.

ID:
7931

Status:
Fixed

Date:
2025/06/14

SynonymManager.AddObservationToGUIDList: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub SynonymManager.AddObservationToGUIDList( PlanObservation )
2: Sub ObservationDatabase.AddObsToGUIDList( PlanObservation )
3: Sub ObservationDatabase.LoadData()
4: Sub ObservationDatabase.Initialise()
5: Function ObservationDatabase.!db.Get() as ObservationDatabase
6: Sub App.Event_Opening()
7: Sub DesktopApplication._CallFunctionWithExceptionHandling()

Resolution:
Fixed.

ID:
7926

Status:
Fixed

Date:
2025/06/14

MainWindow.GetFoVRADec: Nil Object Exception

Exception Type: Nil Object Exception

1: Function MainWindow.GetFoVRADec( MainWindow, int64, int64, byref double, byref double ) as boolean
2: Sub MainWindow.CentreFoVOn( MainWindow, int64, int64 )
3: Sub MainWindow.FoV_MenuAction( MainWindow, CMMCanvas, string, string, string )
4: Sub AddHandler.Stub.27( string, string, string )
5: Function CMMCanvas.Event_ContextualMenuItemSelected( DesktopMenuItem ) as boolean

User description of above error trace:

In FoV tab. Rt-Click image and selected "center on cursor" and got Exception.

Resolution:
Fixed.

ID:
7941

Status:
Fixed

Date:
2025/06/13

Logged objects displayed with zero observations logged

In my observation database (attached) 10 entries for 7 unique objects are listed with 0 (zero) observations logged, even when one or more observations are presents in the observation database. Screenshot attached.

This also means that planfiles containing these object(s) do not highlight an object as observed.

Attachment: Observation DatabaseAttachment: Scherm��afbeelding 2025-05-01 om 15.53.31.jpg

Analysis:
These issues were all caused by bugs in the custom synonym code. That code is the most arcane code in AstroPlanner, designed (sic) to patch over unseen issues with the original catalogues.

Resolution:
Fixed. Hopefully.

ID:
7938

Status:
Fixed

Date:
2025/06/13

AltAzIndicatorCanvas.!Draw: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub AltAzIndicatorCanvas.!Draw( Graphics, double, double, MainWindow, SiteResource, double, boolean )
2: Sub ObservationWindow.obsVisibility_Paint( ObservationWindow, DesktopCanvas, Graphics, Xojo.Rect() )
3: Sub DesktopApplication._CallFunctionWithExceptionHandling()

Resolution:
Fixed.

ID:
7936

Status:
Fixed

Date:
2025/06/13

ObservationDatabase.LoadData: Nil Object Exception

I had tried to run an expired beta version of AP and, as I recall, was appropriately warned about this.

However, I just noted an AstroPlanner Error Log on my desktop that I believe was generated when I had tried to run the expired beta.

I assume the "Nil Object Exception" is unexpected behavior, so please consider this a (belated) bug report.

=====

Version: 2.4.1b2

Expires: 4/4/25

Date: 4/8/25 10:34:32 AM CDT

OS: macOS 15.4.0 (24E248) (ARM) [64-bit app]

Exception Type: Nil Object Exception

1: Sub ObservationDatabase.LoadData()

2: Sub ObservationDatabase.Initialise()

3: Function ObservationDatabase.!db.Get() as ObservationDatabase

4: Sub Sync.UsageData()

5: Sub App.Event_Closing()

Resolution:
Fixed. I think.

ID:
7947

Status:
Fixed

Date:
2025/06/11

MainWindow.SortCompareRows: Nil Object Exception

Exception Type: Nil Object Exception

1: Function MainWindow.SortCompareRows( MainWindow, int64, int64, int64, int64, string, pListBox.SortDirections, byref int64 ) as boolean
2: Function MainWindow.ObjectList_RowComparison( MainWindow, ObjectListbox, int64, int64, int64, byref int64 ) as boolean
3: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

Hi, since I switched to the new release I had to rebuild a complete new database as I got an error on older database triggering the « no show » of all dynamic columns. I was happy with my new database repopulated but unfortunately I just had the same symptom on this brand new database I am using since several months now. Suddenly I have this error and AP shut down abruptly and then when I reopen it the dynamic column do not appear anymore and if I click on it I trigger a fatal error and shutdown

Analysis:
Seems to be associated (sic) with object associations. I can't reproduce it, but I have tightened up the (rather complex) code to avoid this type of exception.

Resolution:
Fixed.

ID:
7943

Status:
Fixed

Date:
2025/06/11

Opening a txt plan file

When I go to open a user contributed plan file that is a .txt file, such as "Burnham_Hya_D.txt", AP provides a Plan Information Window. I click OK and then the plan file window goes away. AP is still running fine as far as I can tell.

Just wondering if there is a setting that I should be toggling to allow txt files to be imported.

Thank you.

Analysis:
Code is wrong. Workaround: Click Cancel instead of OK in the Plan Information dialog.

Resolution:
Fixed.

ID:
7942

Status:
Fixed

Date:
2025/06/11

Not possible copy & paste within all fields

From this version it is no longer possible to Copy & Paste inside all the fields.
In addition, the options in the main menu are also grayed out.

Resolution:
Fixed (I hope).

ID:
7928

Status:
Fixed

Date:
2025/04/11

Imaging Planner script - needs horizontal scroll bar

I'm using version 2.4.1b3 of AstroPlanner on a Mac.
I'm using the "Imaging Planner" script, which is fine.
The problem is that it displays the results horizontally in a window that doesn't have a horizontal scrollbar. To see all the results, I have to export them to an Excel file.
Would it be possible to have a vertical display with a scrollbar?

Analysis:
Not having a horizontal scroll bar is a bug.

Resolution:
Fixed. Horizontal scroll bar enabled. Script modified to "force" vertical formatting as an option.

ID:
7914

Status:
Fixed

Date:
2025/03/20

CTRL+V opens Export Screen

When using the keyboard shortcut CTRL+V to paste text into the Observation Notes under the Observations Tab, the dialog box for Export to Multiple Formats now pop up. This behavior is new with 2.4.1b3.

Attachment: AP Bug.jpg

Analysis:
Sorry about that, I didn't test it enough on Windows. I guess your only workaround would to use the Edit > Paste menu option.

Resolution:
Fixed. Changed the menu shortcut slightly.

ID:
7907

Status:
Fixed

Date:
2025/02/22

Object Find & Replace fields not filling

When trying to populate user fields in a plan file by means of "Object Find & Replace", empty fields will not populate.

Analysis:
Ouch. Bug basically causes any change to a user-defined field to fail silently.

Resolution:
Fixed.

ID:
7908

Status:
Fixed

Date:
2025/02/22

Selecting all sessions in obs database by means of Cmd+A

In the observation database, using Cmd+A to select all session does not work.

Resolution:
Fixed.

ID:
7905

Status:
Fixed

Date:
2025/02/22

MainWindow.Event_CancelClosing: Nil Object Exception

Exception Type: Nil Object Exception
Exception Message: @ H

1: Function MainWindow.Event_CancelClosing( MainWindow, boolean ) as boolean
2: Sub DesktopWindow.Close()
3: Function MainWindow._FileClose_Action( MainWindow ) as boolean
4: Sub DesktopApplication.DoEvents( int64 )
5: Sub ObservationWindow.RestoreObsSessionState( ObservationWindow )
6: Sub ObservationWindow.obs_DoublePressed( ObservationWindow, StripedListBox )
7: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

Editing an object's R.A./Dec. in the observation database.

Analysis:
Interesting one. It looks like the underlying plan document was closed while you were editing. Not sure how.

Resolution:
Fixed. Well, not fixed, since I can't figure out why this occurred. However, if it happens again, the closing of the plan file will be canceled.

ID:
7879

Status:
Implemented

Date:
2025/02/22

Finding the centerpoint of large extended objects

When, in the FoV, trying to find the centerpoint of a large, extended object such as nebulae, open clusters, etc., in order to right click the object to display catalog data and/or its synonyms or to add it to a planfile, it can be difficult to find that centerpoint. Perhaps it would be possible to add the right-click option to an object's label, too.

Analysis:
More of a bug than a feature request.

Resolution:
Implemented/fixed. Extended objects (i.e. those with Size > 0) will be selected if the cursor is within the extended object. If more than one object falls into this category then the one whose centre is closest to the cursor is used.

ID:
7888

Status:
Fixed

Date:
2025/02/08

FoV and objects that lack data

Don't know whether to send this as a bug or as a feature request:

My workflow consists of adding double stars from the WDS catalog to AstroPlanner, using that data to filter out all I need for my observations using Excel, then import single lines for each object back into a new AstroPlanner planfile. By doing so I have an observing guide (after a bunch of macros in Word), a tourfile for my Autostar controller and a nice and clean planfile for all of the doubles without any duplicates.

When importing the data back into AstroPlanner, the lines contain an ID, a Name, R.A. & Declination and Type. No more, as that is all that I need for the planfile. That means all other fields are empty.

The result is that these objects' labels (Name, ID) do not show in the FoV, nor is the object (the star in this case) colored to the color value set under preferences. When I add a magnitude value, they do display with the set color.

Long story short: can a feature be added to make objects always display in the FoV, even when there is no further data for them in the planfile, such as a blank magnitude field?

Resolution:
Fixed. Stellar objects without magnitudes are now drawn in the FoV with a unique symbol to show they no not have a defined magnitude.

ID:
7899

Status:
Fixed

Date:
2025/02/06

MainWindow.Maximise: Nil Object Exception

Exception Type: Nil Object Exception

1: Sub MainWindow.Maximise( MainWindow, boolean )
2: Sub MainWindow.MaximiseTimer_Action( MainWindow, Timer )
3: Sub DesktopWindow.ShowModal( DesktopWindow )
4: Function App.Event_UnhandledException( RuntimeException ) as boolean
5: Sub DesktopApplication._CallFunctionWithExceptionHandling()
6: Sub REALbasic._RunFrameworkInitialization()

Resolution:
Fixed.

ID:
7896

Status:
Fixed

Date:
2025/02/06

Image Manager - Edit User Image Attributes

I added a new User Image to an object and checked it displayed in the Object and Field of View tab. I then went into the Image Manager and edited the description of the image and pressed save. The image remained in the Object tab but failed to display in the Field of View tab.

Going back into the Edit User Attributes revealed that the Image Size parameters were missing. It looks like the Image Size information is not being preserved on an edit. If I repeated the procedure, but when editing the Image description I also re-entered the Image Size info (even though the dialog was still showing the correct data) then all was well.

Please find attached a screenshot of before and after editing the user image description.

Resolution:
Fixed.

ID:
7889

Status:
Implemented

Date:
2025/02/02

Exporting - use multiple settings

Currently, exporting data from AstroPlanner can be done using a self created preset, selected in the exporting dialogue window under "Settings - Load".

Would be very useful if multiple user settings could be selected, instead of only one, to batch export data in varying format simultaneously.

Resolution:
Implemented. File > Export > Multiple Generic Text, Excel, XML, or JSON files...
This allows you to apply multiple (pre-made) export settings files to the current plan document.

ID:
7891

Status:
Fixed

Date:
2025/01/30

ObjectListbox.CellTextAt: Out Of Bounds Exception

Exception Type: Out Of Bounds Exception

1: Sub ObjectListbox.CellTextAt( int64, int64, assigns string )
2: Sub MainWindow.NextInlineCell( MainWindow )
3: Sub MainWindow.InlineTimer_Action( MainWindow, Timer )
4: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

Entered text in a user field, hit the Return key on my keyboard and this exception popped up.

Resolution:
Fixed. I modified the code a bit to make it more robust, and added a bunch of debug stuff that will help next time this happens.

ID:
7900

Status:
Implemented

Date:
2025/01/29

Show session user-defined field values under the session list

Show any session user-defined field values for a selected session under the session list in the observation database window.

Resolution:
Implemented.

ID:
7901

Status:
Fixed

Date:
2025/01/29

Only user-defined session definitions with at least one actual value are displayed in the session list as a column

Only user-defined session definitions with at least one actual value are displayed in the observation database window session list as a column. Otherwise the column is not displayed.

Resolution:
Fixed. Both defined and undefined user value columns are now displayed.

ID:
7895

Status:
Fixed

Date:
2025/01/01

Bug/Feature/Exception email issue

Fixes a problem introduced in the last beta that "bounces" any messages sent from the application.

Resolution:
Fixed.

ID:
7894

Status:
Fixed

Date:
2024/12/20

Ioptron CEM40 needs baud rate of 115200bps

My mount is an Ioptron CEM40 which requires 115200 bps baud rate
It uses the same commands as the CEM60 and connects ok with NINA or MaximDL

It will not connect to Astroplanner 2.4 as the baudrate is fixed at 9600 when an Ioptron mount is selected.

Resolution:
Fixed. You can now select the bit rate of the serial port with iOptron mounts.

ID:
7892

Status:
Fixed

Date:
2024/12/16

User Defined Date/Time field problem

Done some more research and it appears that the only user field I use which defined as a Date time field when displayed in the object list as a column has the time element of the value from NOW - the script is loading it with full date and time of the next setting time for the object (with adjustments).
I have sorted out a workaround of storing the data and time as an SQLDateTime() string and Parsing this to recover it in later reports I generate in the script.

Resolution:
Fixed.

ID:
7886

Status:
Fixed

Date:
2024/12/16

EquatorialCoordinates.Operator_Compare: Nil Object Exception

Exception Type: Nil Object Exception

1: Function EquatorialCoordinates.Operator_Compare( EquatorialCoordinates ) as int64
2: Function GotoDialog.GetRADec( GotoDialog, byref double, byref double ) as boolean
3: Sub MainWindow.CentreFoVAtCoordinates( MainWindow )
4: Sub MainWindow.FoV_MenuAction( MainWindow, CMMCanvas, string, string, string )
5: Function CMMCanvas.Event_ContextualMenuItemSelected( DesktopMenuItem ) as boolean
6: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

Attempting to center a position by entering a B1950 R.A./Dec. in the FoV. This exception pops up and the position entered is not centered.

Resolution:
Fixed. I think.