Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

In alarm-edit window, make tapping outside of the window do nothing

未关闭 适合新手
#446 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 7 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
72/100
Issue 类型
功能
描述清晰度
描述清楚
活跃度
冷清
技术栈
android, kotlin
领域
mobile

调研方向

由于负载中没有提及任何文件,请先在 Kotlin 源码中搜索闹钟编辑对话框以及处理对话框外部点击的代码。找到对话框的创建位置,并检查它是否可以通过外部点击关闭。修复方法是阻止这种关闭方式,同时保持“确定”和“取消”正常工作。当外部点击后编辑器仍保持打开,且“确定”和“取消”的行为与之前一致时,即视为完成。

由索引模型根据 Issue 内容生成。

描述

feature request needs triage
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

Make it impossible to close the alarm-editing window by tapping next to it; that is, tapping outside of the window does nothing. This means you have to explicitly click OK or Cancel to leave the editing window.

Why do you want this feature?

When modifying an alarm in the pop-up window, it is possible to tap outside of the window. This discards any modifications without warning (making it equivalent to clicking Cancel). The action of tapping a window away does not feel destructive, though. As a result, I have thought on multiple occasions that I successfully edited an alarm, whereas I later discovered that nothing was changed.

Making tapping away equivalent to OK instead of Cancel is not a good idea either, because one might deliberately want to click away to discard a change. And a Discard changes? pop-up is overkill. Hence my suggestion.

Additional information

No response

主要语言
Kotlin
星标
706
派生
73
平均合并
5 天 17 小时
30 天内合并 PR
8

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

FossifyOrg/Clock 的其他 Issue

查看 FossifyOrg/Clock 的全部 Issue

相似的 Issue

更多 Kotlin Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。