AstroPlanner Beta Testing

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

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

Status:
Fixed

Date:
2024/12/04

Issue with Synscan GoTo driver

Synscan driver issues badly formatted slew messages on some mounts.

Resolution:
Fixed.

ID:
7866

Status:
Fixed

Date:
2024/10/26

Vertical size change of Object list and Observations lists is not responsive

In the Observations window, when Widgets are showing, dragging the "handle" to increase the vertical height of the Object list section (and thereby decreasing the height of the Observations list section) results in the inability to reverse the change and decrease the height (back to where it was) of the Object list section.

Furthermore, the vertical height of the Object section jumps in size such that only 2 or 3 Observations can be seen unless the Observations list is scrolled.

This is very annoying if 3 or more Observations of an object are present because the Observations section has been made too "short" and can't be changed back to a useful height.

Turning off the Widgets display allows one to increase and decrease the height of the Object list section as expected. Also, there is no "jump" when changing the vertical height.

Resolution:
Fixed.

ID:
7831

Status:
Fixed

Date:
2024/10/17

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 DesktopListBox.Sort()
4: Sub MainWindow.SortObjectList( MainWindow )
5: Sub MainWindow.MultiSortObjectList( MainWindow, boolean )
6: Sub MainWindow.SortObjects( MainWindow )
7: Sub MainWindow.SortListPopup_Action( MainWindow, SelfLoadingPopup, string )
8: Sub SelfLoadingPopup.Event_Action( string, int64 )
9: Sub APPictureButton.DoAction( string, int64 )
10: Sub APPictureButton.Event_Pressed()
11: Sub DesktopApplication._CallFunctionWithExceptionHandling()

User description of above error trace:

I am doing some experiments: I tried to sort the list of a plan with the button at the bottom « sort list » on the transit time. The same error happens as when I click on the head of the column. I tried to save the plan (created with the former version) and reopen it but the problem stays the same.

Resolution:
Fixed. Hopefully.

ID:
7865

Status:
Fixed

Date:
2024/10/17

GotoDialog.GetRADec: Nil Object Exception

Exception Type: Nil Object Exception

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

User description of above error trace:

In the FoV "center FoV at coordinates" window, I accidentally entered the value "60" in the declination seconds window.

Resolution:
Fixed.

ID:
7873

Status:
Implemented

Date:
2024/10/17

Selecting objects in the WDS catalog

The WDS catalog is perhaps unique, in that different components of a double star have identical ID's.

When extracting the information for all components of a double star, it would be very useful if the search would result in all components of that double star (read: all matching ID's) were selected.

For example, the double star STF123, per attached screenshot: it has 4 components (A through D), all of which currently need to be manually selected to be added to a planfile. The search function in a catalog (the WDS specifically, but perhaps other, too) would benefit greatly from a user selectable option "select all objects with matching ID's".

Attachment: VAvW 2024-10-06 om 09.56.07.jpg

Resolution:
Implemented.

ID:
7876

Status:
Implemented

Date:
2024/10/15

Remove requirement for SMTP parameters

Remove the requirement to specify an outgoing SMTP service to send messages to AstroPlanner support.

Resolution:
Implemented.

ID:
7874

Status:
Implemented

Date:
2024/10/10

Add KStars as an external (planetarium) app

Add KStars as an external (planetarium) app. Mac and Windows.

Analysis:
Can only sync Kstars' FoV to reflect AstroPlanner's - not the other way around (at this time).

Resolution:
Implemented.

ID:
7868

Status:
Fixed

Date:
2024/09/25

Script no longer working as before

These two lines of code no longer work in latest beta version 2.4.1b1

ImageTime = ImageTime.ParseDate(obj.UserField(TargetNumberFieldName).Value)
Plan().LocalDateTimeSynchronous = ImageTime

definition of ImageTime
dim ImageTime as new Date

ParseDate always returned the Date and time form of the string stored in the UserField

The Plan display then updated correctly after recalculating the plan for this date and time.

Now this fails silently and the plan reverts to the current date and time - causing a total failure of the script logic

Will have to revert to previous beta of Astroplanner where the same script works perfectly

Resolution:
Fixed.

ID:
7871

Status:
Implemented

Date:
2024/09/25

Add additional eyepiece to printed Finder Charts

Add at least one additional eyepiece to printed Finder Charts, so I can show medium and high magnification.

Resolution:
Implemented. Added 3 additional eyepiece options. If chosen, the largest FoV eyepiece will define the field of view, and the rest will be drawn as annotated circles within the field of view.

ID:
7870

Status:
Fixed

Date:
2024/09/23

ASCOM Unparks the telescope on connecting

When the telescope is connected (and ASCOM is used), AstroPlanner tries to Unpark the mount, when it wasn't previously parked causing the mount to slew uncontrollably.

Analysis:
Forgot to check AtPark before attempting to Unpark. Note that this is only an issue with scope mounts that can be parked.

Resolution:
Fixed. Verified by Peter G.

ID:
7863

Status:
Fixed

Date:
2024/08/26

Searching for PK027-03.2 does not succeed

Searching for PK027-03.2 does not succeed, even though there is at least on catalogue containing it.

Analysis:
An issue with PK and PNG object searches.

Resolution:
Fixed.

ID:
7829

Status:
Fixed

Date:
2024/08/24

Long term visibility widget shows black crosses

Version 2.4 release. Also was in 2.4b25.
If horizon is enabled, some of the red crosses are shown as black (whether the item is below the specified horizon or not).

Analysis:
Not (completely) fixed in V2.4.1b1. There's an issue if an upper horizon is used.

Resolution:
Fixed. Issue no longer occurs if an upper horizon is defined.