well, a few of these dbus functions needed some overhaul. I actually just removed setSolverSearchCoords. Long term solution is the ability to set and store options, but for now, you have:

1. setSolverArguments
2. getSolverArguments

so you can use getSolverArguments and then edit it to change radius and set it again. Please beware this is transient only, it is not stored. For example, if the mount is slewed to another location, the solver settings will be generated again from the stored settings. So you will have to set any custom arguments before you call captureAndSolve. Hopefully I will find a way to provide access directly to the stored options.

Rendering Error in layout Message/Item: array_keys(): Argument #1 ($array) must be of type array, null given. Please enable debug mode for more information.

Please Log in or Create an account to join the conversation.