Ehem... Mine is not loading them.
I.e. It loads default connection params properly - and that is fine as they are set to default scope configuration.
But my scope is configured differently - and I assume someone may want as well the scope to connect to
their observatory AP instead of creating its own network (which is not very good). So the connection data must
be loaded and it needs to be different from the defaults.
Am I missing something?
Sorry. Nexstar evolution/AUX driver.
If it is supposed to work it is probably my fault. I am pretty new to the driver development.
So, is it supposed to load the saved setup on start-up of the driver?
What about default values we may want to be there?
So should I invoke load function on driver init?
The properties are IP address and port for the mount.