- edited description
Image File Pattern Entry Not Getting Saved
Release 1.10 Build 074 and Build 075.
Windows 7 Pro x64 w/ all patches and updates. Also Windows 10 Home x64 w/ all patches and updates.
Description
On a PC that’s ‘never’ had N.I.N.A. installed user selected Pattern Names that have been ‘appended’ to the default Image File Pattern are not being saved. Example – if you select $$APPLICATIONSTARTDATES$$ or anything else and append it to the default Image File Pattern then immediately close N.I.N.A. and reopen N.I.N.A. you will find that it no longer shows up as being appended to the Image File Pattern name. Note – the Image File Path has not been populated yet and no other N.I.N.A. customization's have been made.
The PC must never have had N.I.N.A. installed. If you do this on a PC that has had N.I.N.A. installed, N.I.N.A must be removed via Windows Program and Features, the NINA directory deleted under %USERPROFILE%\AppData\Local\ and temp NINA files under %USERPROFILE%\AppData\Local\Temp deleted.
Steps to Reproduce
- Install N.I.N.A on a new PC or PC that was cleaned of all N.I.N.A. files.
- Use the Default Profile.
- Go to Options => Imaging then Pattern Names.
- Append $$APPLICATIONSTARTDATES$$ or anything else to the default Image File Pattern. Do not make any other customization's such as entering an Image File Path or anything else.
- Immediately close N.I.N.A. (X).
- Reopen N.I.N.A. and go to Options then Imaging. The appended $$APPLICATIONSTARTDATES$$ or anything else should be missing.
- Repeat steps 2 – 6 multiple times…
I did steps 3 to 6 above six or seven times and the appended Pattern Name only showed up once.
Expected Behavior
The appended $$APPLICATIONSTARTDATES$$ should be there.
Actual Behavior
The appended $$APPLICATIONSTARTDATES$$ or any other Pattern Name is missing from the default Image File Pattern.
I can make a video of N.I.N.A. doing the above if necessary…
Comments (12)
-
reporter -
reporter - edited description
-
Jim, it would appear that you don’t have ASCOM installed, or installed properly.
Go here: https://www.ascom-standards.org/
and ensure that ASCOM Platform 6.4SP1 is installed.
-
reporter Dale - thanks for getting back to me. I am using ASCOM now for my mount, focuser, imager, filter wheel …etc. Should I remove and reinstall?
-
reporter I will remove and reinstall.
-
repo owner Did you append the image pattern via drag&drop or double clicking the list or by manually entering it?
-
reporter Dale - I ran the ASCOM Diagnostics and got errors. I tried to remove from Windows and it wouldn’t remove cleanly. Something must be going on with my PC. Considered this closed for now if nobody else is seeing this problem. Thx
-
reporter Stefan - Double Clicking. But see the post to Dale. Something is going on with my PC’s Registry. ASCOM wouldn’t remove cleanly.
-
repo owner Sure Jim - The ASCOM stuff is a different issue, but NINA can run just fine without ASCOM.
The problem you are seeing is due to the double click and there I can reproduce this issue (and fix it)
-
reporter Good news Stefan. Thx
I also had problems removing SGPro last month when I decided to move to NINA full time. I had to delete SGPro manually and scrub the registry. My PC is almost 7 years old with the original SSD.
-
It’s often common to leave residuals after a uninstall. I have a program that alerts me when this happens and will optionally allow my to “clean” the uninstalled program properly. I had to get this when a driver was not being uninstalled cleanly during an update.
The program I think is by EASEUS. It removes remnants of uninstalled files/registry.
-
repo owner - changed status to resolved
fixed in latest beta
- Log in to comment