When using the timer, you cannot take a picture ahead of time, but only interrupt the process
还没有人认领这个 Issue。
评估
调研方向
The payload names no files or tests. Start by reproducing the timer flow in the app: begin a countdown, then check that the shutter button turns into a cancel button. Decide whether a second press during the countdown should capture immediately, and confirm the maintainers agree before coding. Done means a press during the countdown takes the photo now, and the existing timer behaviour still works when nothing is pressed.
由索引模型根据 Issue 内容生成。
描述
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
I propose to discuss the feasibility of changing the current functionality of creating a photo using a timer.
Why do you want this feature?
I usually take pictures using a three-second delay. But I have situations when I have already started the countdown and I need to take a picture at that very moment, without waiting for the countdown to end (because then the right moment will be missed). At the moment, it is impossible to take a picture like that, because the camera shutter button changes to a cancel button after the countdown has started.
Additional information
Fossify Camera 1.1.0 (6) f-droid (Jul 28, 2025)
- 主要语言
- Kotlin
- 星标
- 473
- 派生
- 56
- 平均合并
- 2 天 7 小时
- 30 天内合并 PR
- 5
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
FossifyOrg/Camera 的其他 Issue
-
feature request needs triage
难度 4/5 3-5 天 新手友好度 45/100
FossifyOrg/Camera#347 ·
-
feature request needs triage
难度 5/5 一周以上 新手友好度 35/100
FossifyOrg/Camera#346 · 1 条评论 ·
-
bug needs triage
难度 4/5 3-5 天 新手友好度 48/100
FossifyOrg/Camera#339 · 1 条评论 ·
-
bug needs triage
难度 4/5 3-5 天 新手友好度 25/100
FossifyOrg/Camera#338 ·
-
feature request needs triage
难度 5/5 一周以上 新手友好度 30/100
FossifyOrg/Camera#335 ·
查看 FossifyOrg/Camera 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
saisaharsh3/Leftovers#13 · 1 条评论 ·
-
难度 1/5 1 小时以内 新手友好度 67/100
navikt/esyfo-narmesteleder#700 ·
维护者通常 1 天内回复
-
A2A agent card served at agent.json, but A2A 0.3.0 uses agent-card.json可能已有人在做 @hadirsa 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 75/100
embabel/embabel-agent#2142 ·
维护者通常 1 天内回复
-
bug feedback required
难度 2/5 1-3 小时 新手友好度 66/100
streetcomplete/StreetComplete#7275 · 3 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
Kotlin/kotlin-lsp#288 ·