Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Need camera-model specific overlay configuration files #3250

Open
EricClaeys opened this issue Dec 29, 2023 · 0 comments
Open

[BUG] Need camera-model specific overlay configuration files #3250

EricClaeys opened this issue Dec 29, 2023 · 0 comments
Assignees
Milestone

Comments

@EricClaeys
Copy link
Collaborator

EricClaeys commented Dec 29, 2023

There are currently two overlay configuration files - one for ZWO cameras and the other for RPi cameras.
There should be a different file for each Camera Model so when users switch models (which usually have different resolutions) fields can be placed in the correct place.

Ideally when a user switches to a new Camera Model that doesn't yet have a configuration file, one would be created based on the prior Camera Model if it exists, or else on the generic Camera Type configuration file. Either way, any field in the new file that is outside the image size should be moved into the image.

The above would happen during installation if a new Camera Model us detected. A function or utility script that is called from install.sh or from makeChanges.sh should check for the correct file and create it if needed.

@Alex-developer Alex-developer added this to the v2024.xx.xx milestone Dec 29, 2023
Alex-developer added a commit that referenced this issue Feb 4, 2024
Alex-developer added a commit that referenced this issue Feb 8, 2024
Alex-developer added a commit that referenced this issue Feb 9, 2024
Alex-developer added a commit that referenced this issue Mar 5, 2024
Alex-developer added a commit that referenced this issue Mar 5, 2024
Alex-developer added a commit that referenced this issue Mar 8, 2024
Alex-developer added a commit that referenced this issue Mar 8, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 10, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Alex-developer pushed a commit that referenced this issue Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants