My one line change was merged in for the INDI Library v1.9.5 release. I don't think there's anything else to be done in INDI - I wouldn't change the default or enforce the SDCard Delete due to the limited testing and the potential for Fuji to change the behaviour for future models.

It would be useful to document driver quirks / specific configuration requirements so that new users don't have to 're-invent the wheel' but where would be best for this? The KStars Handbook is the most user accessible place but doesn't contain any device documentation (correctly in my opinion). Upstream for the driver may be ideologically best which would be at github.com/gphoto/libgphoto2/tree/master/camlibs/fuji but then this is really hard for users to find and the content, style & maintenance is down to others, so maybe it should be at github.com/indilib/indi-3rdparty/tree/master/indi-gphoto ?

Maybe we could add a few links to INDI driver documentation in the 7.7 INDI Frequently Asked Questions section of the KStars Handbook? The trouble is that INDI driver documentation is non-existent for many of the drivers and depends entirely on the developer. I feel that this is one area that limits adoption of the whole INDI ecosystem for non-technical users. I don't know what the solution to that would look like - maybe more user guide / workflow style documentation for INDI drivers? This could be a large undertaking but maybe a format template and a few simple example cases would be a good start?

Thoughts / opinions?

Read More...