feature request: Separate save location for videos
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
The payload names no files, so start by searching the Kotlin Android sources for where captured videos are written and where the save-location setting is read. The issue proposes a toggle that, when on, asks for a separate video folder, with the current merged behaviour kept as the default. Done means that toggle exists, videos go to the chosen folder, and photos are unchanged. Confirm the design with a maintainer first, since no one has replied in 548 days.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Checklist
- I made sure that there are no existing issues - open or closed - to which I could contribute my information.
- I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
- I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
- I have taken the time to fill in all the required details. I understand that the request will be dismissed otherwise.
- This issue contains only one feature request.
- I have read and understood the contribution guidelines.
Feature description
An option to save videos taken with Camera to a separate location than photos
Why do you want this feature?
I often find myself moving videos from a pictures folder to a video folder just because there isn't the option to save them separately. It would be very useful and save a lot of time.
Additional information
What I consider "the best approach" would be a toggle like "Save videos separately from photos" and only when that's enabled the user is asked to provide a location to save videos. Otherwise just keep functionality like it is now with the merged save location.
- Lenguaje dominante
- Kotlin
- Estrellas
- 473
- Forks
- 56
- Merge medio
- 2 d 7 h
- PR fusionados (30 d)
- 5
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de FossifyOrg/Camera
-
feature request needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
FossifyOrg/Camera#347 ·
-
feature request needs triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
FossifyOrg/Camera#346 · 1 comentario ·
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
FossifyOrg/Camera#339 · 1 comentario ·
-
bug needs triage
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
FossifyOrg/Camera#338 ·
-
feature request needs triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 30/100
FossifyOrg/Camera#335 ·
Todos los issues de FossifyOrg/Camera
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 3 días
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
lugassawan/swe-workbench#799 ·
Los mantenedores suelen responder en 1 día
-
Default book icon displayed while loadingPosiblemente ocupada @Bhaskar-Guthula-137 la tomó hoy. Abiertobug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
kiwix/kiwix-android#5194 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
jellyfin/jellyfin-androidtv#5885 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 73/100
tortuvshin/open-apps#377 ·
Los mantenedores suelen responder en 1 día