Hi All,
I am experiementing with implementing a standalone viewer for INDI cameras outside of Kstars. As Python is my preferred language I based my work on DCD , because I prefer not to use a C binding.
I still run Kstars to control the CCD settings. So, whenever my viewer requests an image it will also be displayed in Kstars FITS viewer. Am I doing it wrong? Could that be prevented?
BTW, I get a similar issue when switching to the Guide tab in Kstars/Ekos, where I often use the "loop" feature to focus my cameras (when streaming is unavailable or prone to crashes). When switching to the "INDI control panel" and taking an image it will still end up in the Guide tab and not in a seperate FITS viewer.
I assume it is a design flaw of INDI that a client cannot register and deregister for a specific BLOB source. If I am not mistaken, a client receives all BLOBs when it does an "enableBlob". Well, ok, the client could filter and decide if it is currently expecting an image from that source or not.
Cheers
Guido
I am experiementing with implementing a standalone viewer for INDI cameras outside of Kstars. As Python is my preferred language I based my work on DCD , because I prefer not to use a C binding.
I still run Kstars to control the CCD settings. So, whenever my viewer requests an image it will also be displayed in Kstars FITS viewer. Am I doing it wrong? Could that be prevented?
BTW, I get a similar issue when switching to the Guide tab in Kstars/Ekos, where I often use the "loop" feature to focus my cameras (when streaming is unavailable or prone to crashes). When switching to the "INDI control panel" and taking an image it will still end up in the Guide tab and not in a seperate FITS viewer.
I assume it is a design flaw of INDI that a client cannot register and deregister for a specific BLOB source. If I am not mistaken, a client receives all BLOBs when it does an "enableBlob". Well, ok, the client could filter and decide if it is currently expecting an image from that source or not.
Cheers
Guido