Hi Jasem
This is an interesting discussion and gives some insights into the coding of KStars and INDI.
BUT: I still don't understand, why the device manager keeps listing a wrong version number! (KStars and INDIlib on localhost!)
I tried to debug KStars and could trace down the calls in "drivermanager.cpp".
The "debug-version" of KStars (Debugging in QT Creator) reads the correct version from "indidrivers.xml". But the very same binary (produced by QT Creator debugger) started by hand does always return the driver version I got debugging in QT Creator, in spite of a handmade change in "indidrivers.xml". This change will be reflected, ONLY if I start a new debugger in QT Creator. From this time on - starting kstars directly from command line - brings always the version number read before in QT Creator.
New information (25.12.19) for Jasem and Kaczorek:
I found a notice from Kaczorek (
www.indilib.org/forum/ekos/2137-device-n...le-editor.html#16059), that states exactly what i'm referring to! The contribution dates two years ago and apparently nothing has changed!
This strange behaviour is not crucial, but bothersome. Especially when you want to check against a correct driver version. Unfortunately Kaczorek didn't follow the case, so we are none the wiser. There is definitively some caching of "indidrivers.xml", but by now I cannot spot where. I hope, we can track down it!
Sincerely
Antonio