Moveable Recording Timer
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
Research direction
The payload names no files, so begin by locating the recording timer view in the Kotlin Android source and the existing settings code that controls camera UI options. Done means a setting chooses between the two positions: beside the record button, or at the top of the screen offset below any camera notch. Expect to read around the layout code before editing, and confirm the chosen placement on a device or emulator.
Written by the indexing model from the issue text.
Description
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 would like to be able to change where the recording timer (the stopwatch that shows when you start recording) goes. It would be great to have an option to either place it near the record button or at the top of the screen (pushed down slightly to account for any camera notches on the phone).
Why do you want this feature?
Many people are used to looking at the top of the screen for the recording timer, while some are used to having it near the record button. Having an adjustable option makes the camera layout easier to use for different people.
Additional information
No response
- Dominant language
- Kotlin
- Stars
- 473
- Forks
- 56
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 8
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from FossifyOrg/Camera
-
Custom Shutter SoundOpenfeature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 35/100
FossifyOrg/Camera#357 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
FossifyOrg/Camera#347 ·
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 5/5 Over a week Newbie friendliness 35/100
FossifyOrg/Camera#346 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 48/100
FossifyOrg/Camera#339 · 1 comment ·
Maintainers usually reply within 1 day
-
bug needs triage
Difficulty 4/5 3-5 days Newbie friendliness 25/100
FossifyOrg/Camera#338 ·
Maintainers usually reply within 1 day
All issues in FossifyOrg/Camera
Similar issues
-
afk-ok area:data-quality importer size:S
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
enorm-labs/event-junkie#3301 ·
Maintainers usually reply within 1 day
-
MDM: interfaceName cannot be set through managed configurationsPossibly taken @JulienUsson claimed this today. Openbug
Difficulty 1/5 Under an hour Newbie friendliness 82/100
bk138/droidVNC-NG#404 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
rustyrazorblade/easy-db-lab#1017 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
openclaw/openclaw#172218 · 1 comment ·
Maintainers usually reply within 1 day