@ Development Team
Thanks a lot!
you pointed me in the right direction.
Finally I used Synaptic to install libraw-dev while downgrading the libraw package.
@ El Corazon
thank you for your suggestion.
I issued this command but the problem with the dependency of libraw-dev persists.
libraw-dev depends on libraw19 (= 0.19.5-1ubuntu1) but 0.19.6~202002010816~ubuntu20.04.1 should be installed
I am still able to build KStars, so -luckily- this is no showstopper but I thought I report it back (for what it's worth).
I had two clear nights since the end of September (6.11.2020 and 7.11.2020 = 11/6 and 11/7) and KStars worked like a charm.
just a side note:
You have updated the dependecy list in the README.md
On KDE neon I get this error message:
Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) libraw-dev:amd64 < none -> 0.19.5-1ubuntu1 @un puN Ib >
Broken libraw-dev:amd64 Hängt ab von on libraw19:amd64 < 0.19.6~202002010816~ubuntu20.04.1 @ii mK > (= 0.19.5-1ubuntu1)
Considering libraw19:amd64 10 as a solution to libraw-dev:amd64 9998
Die folgenden Pakete haben unerfüllte Abhängigkeiten:
libraw-dev : Hängt ab von: libraw19 (= 0.19.5-1ubuntu1) aber 0.19.6~202002010816~ubuntu20.04.1 soll installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.
See this thread: New Internal Solver for Mac, Windows, and Linux -- Testing/ Experiments needed posts on page 45 from post number 62184 onward.
Try to install a newer version of stellarsolver.
Kstars refrence is amazing and proves that the source code is painstakingly commented. Without doubt KStars is a professional-grade program. I am curious: how many lines of code have been written? How many hours were spent during two decades to create this program?
That's pretty cool stuff.
I tried to build the API reference with doxygen.
What I did was really easy.
You must use the terminal.
1. Install doxygen.
sudo apt install doxygen
2. Install graphviz
sudo apt install graphviz
3. Go into the kstars directory and execute
doxygen -g doxy.cfg
You can choose every filename you want.
4. Make some changes to doxy.cfg
I made these changes:
PROJECT_NAME = "KStars"
OUTPUT_DIRECTORY = /home/your_name_here/doxy-kstars
RECURSIVE = YES
Save your changes.
The result is in the ouput folder and you get a nice reference with graphs.
There is certainly more to it. But I have no clue.
Reading the source code makes me
The groundwork has to be laid first, time will tell.
Yes, it looks funny.
This is the ortographic projection which resembles a marble.
And - being a marble the left most obstruction should become invisible.
Instead it was flipping over to a different part of the night sky. On the second picture it covers Pegasus.
I will not abandon all hope that this will be improved
I'am playing with the artificial horizon manager.
This does not look right. The obstacles - they appear to be defying gravity.
You are right, that's a viable soltution for the time being. Now I have to spend some time to setup my artificial horizon.
On the other hand, if the Celestial equator can be plotted it must be possible to plot another circle at the angle of declination above or under the celestial equator which describes the target's altitude.
ok the skyview could be useful for planning a session. But one important part of the puzzle is missing - or not?
On the skyview I can show the Celestial equator and the Celestial meridian. I can find a target and the bulls eye marks the target. I can show the artifical horizon. But, the missing part is the path of my target on the sphere. This would be really useful information (together with time and altitude for any given point on the path)!
thank you for pointing me to the Artificial Horizon Manager. This is exactly the kind of table list I had in mind.
But I used it and recognized that the created obstacle does not show up in the AvsT tool.
The obstacles are only visible on the skymap. I tried to plan a session with the skymap. But it is not intuitive. I can go forward in time, but I cannot slew the mount to this position of the object in the future. I would like to do this in order to have a look if the scope is pointing to the wall, roof, tree or free part of the sky. Maybe this could be changed?