Rob I tested the latest build fir about two hours. I didn't find any new bugs. Good job!
But there are two minor issues I want to bring up:
1. While I can change the scope and guidescope focal length in the mount control screen, they never save. The save button seems to work, but when I start Kstars back up the original focal length settings come back.
2. In the Mosaic feature, I like new feature where I can move the mosaic around to compose it, I don't see any way to zoom the screen in or out. I was looking at my 2x2 composition and it filled the screen - but I really wanted to see more of the sky so I can judge exactly how I wanted to position the mosaic. A zoom in/out function like you have in the planetarium would be really helpful. I thought spinning the mouse scroll wheel would do it, but no.
iOptron CEM120 EC2 and CEM25P
Celestron C11 EdgeHD
William Optics Star71
ASI 1600Mm Pro, ASI 462MC
Moonlight motorfocus & Esatto focuser
LodeStar X2 and ZWO OAG
I'm glad to hear it all worked out! As for your two minor issues, I am not sure I can help with those right now. I am surprised that the scope focal length and guide scope focal length do not save. Did KStars crash before you restarted it? Sometimes I note that if there is a crash and it doesn't get shut down properly, some preferences don't save. But if that isn't the problem, I am not sure I know. You might try posting in a new forum post.
For the second item, that is a new feature that I don't have any experience with. I have had my head very deep in the building and packaging scripts and code and I haven't even gotten to play with any new features recently, (plus it is full moon). You might want to ask Jasem or post in the general forum, since I think he is the one who might have worked on that.
Rob, yes on INDI startup. It's intermittent, but maybe 2 or 3 times a week I click connect and blammo! KStars is gone. Then I restart KStars and click connect and I get the message that there's already an INDI server running and then I can connect to that and everything's fine.
I figured it was just something flaky with my setup until I read the description of this exact problem in this thread.
Guess I should run in gdb and see if I can document it better.
I have experienced also intempestive crashes of KStars since a few months and I reported it.
The crashes occurred especially while running the simulators.
I think I finally found the culprit : kstarsrc
This file kstarsrc is located (on a Mac) at Library / Preferences / kstarsrc. It contains all the user preferences.
I deleted this file and I've got no crash since in the simulators profile or the real profiles.
I recommend not to delete immediately this file but saving it by changing its name.
When you will start KStars again, the Startup Wizard will open and will recreate a new kstarsrc file.
So as in all the drivers, there is the "Options" tab where you can save, and load configurations in the INDI driver. Is that what you are using to do the saving and loading? I just tried it myself, though I don't have a weather device. I was able to set the port, save the configuration, close the driver, then load it again. Now most drivers I have been familiar with in the past have automatically loaded the configuration. Is this one any different?
Hmm, Jean-Claude, you might be on to something. I just tried your experiment, renaming my kstarsrc file and then tried starting an indiserver in KStars. It crashed with the old one very easily, it didn't crash with the new one when I tried it a couple of times. I'm not sure this was a well conducted experiment since I really need to do it many times in a more controlled way, but it's enough that I think you might have something here. We should see if there is some setting that got saved in there that somehow affected it. It's easy to check, it is literally a text file full of settings.
I just did a diff between the old and the new kstarsrc and looked through the differences in settings. Many of them would almost certainly not cause any crashes, such as the window size being different. But one thing that stood out is that I had logging turned on in my kstarsrc that was causing a crash. Specifically I had turned on Verbose logging with CCD checked. I did some tests and that seems to cause a crash about 50% of the time, but without it being checked, it doesn't cause a crash, at least that I see with a couple of quick tests. Can you check to see if you have that setting enabled when using the settings file that caused the crash? Or maybe just try opening KStars, turning on CCD logging and see if that reliably crashes it for you? If so, we may have found a major clue as to what causes my mysterious crash that was seemingly affecting just me.
Hi Rob,You might be right about the cause of the troubles and the logging settings.When there is no logging, there is no crash.I attach 3 kstarsrc files in a zip folder :- kstarsrc working : this file has been obtained after a de novo installation of KStars. No crash in simulator configuration or in real configuration. With this file all logs are OFF. Numerous trials on 2 Macs.- kstarsrc crash : this file is my old file causing random crashes. With this file all logs are ON. Numerous trials on 2 Macs.- kstarsrc working then damaged : this file is the damaged kstarsrc working file obtained AFTER having run KStars with the kstarsrc crash file !May be the GPS log is the culpritLast october I opened a topic on serial-USB drivers (indilib.org/forum/mounts/10576-do-not-us...e-setup.html?start=0)and PDB (indilib.org/forum/mounts/10576-do-not-us....html?start=12#76767) pointed on some solution around the GPS driver.This helped solving my disconnection problems by simply choosing the “Celestron GPS" driver instead of the "Celestron NextStar" driver.I hope we are on the trackHave a nice day Rob.
Following the suggestions in this thread, I removed my kstarsrc and it works now! There were a couple of settings in my old kstarsrc concerning CCD and my ZWO ASI. I think those were the problem. I can connect locally and remotely to all my gear again.