I have recently started using 1200 second exposures for narrowband.
There are three issues with this...
1) When incrementing the exposure times it jumps from 900 to 3600 seconds - intermediate steps of 1200 and 1800 would be nice and even better if this was configurable.
2) When any value over 900 seconds is set and you go to any other tab and then back to the camera tab it always sets the exposure time back to 900 - this is very annoying. Also, if you have a Type other than 'Light' set, it resets it to 'Light'.
3) When logging the exposures at the bottom of the window it has started displaying the times in an exponential format.
Further, and I am not sure if this is related, when taking exposures which restart when the guiding exceeds a limit, the exposure counter if being randomly reset back to zero. I have only started seeing this happen when using 1200 second exposures.
Last edit: 5 years 6 months ago by Paul. Reason: correction, expansion and new information
1. This is because you use the spin arrows and not a digit entry, correct? So you require additional intermediate values?
2. Isn't this because you are not actually editing the job you want to modify? When you are in edit mode, the "+" button changes to a check, to validate your changes. Please confirm.
3. I have a differential pushed in review to fix that sort of thing and properly support locale characteristics. But the dust needs to settle first on kstars-bleeding.
4. The count reset issue is fixed and tested OK on my side, but the differential might not be merged yet. Stay tuned for this.
1. This is because you use the spin arrows and not a digit entry, correct? So you require additional intermediate values? Yes or the ability to configure it for my own use.
2. Isn't this because you are not actually editing the job you want to modify? When you are in edit mode, the "+" button changes to a check, to validate your changes. Please confirm. No, this happens whether I use use the up/down buttons or edit it directly - any value over 900 gets set back to 900. It can be seen in simulated camera as well.
3. I have a differential pushed in review to fix that sort of thing and properly support locale characteristics. But the dust needs to settle first on kstars-bleeding. I am building locally on Raspbian but the latest kstars build is failing.
4. The count reset issue is fixed and tested OK on my side, but the differential might not be merged yet. Stay tuned for this. Will do.