Feature Request: Action toggle, quick‑record, scene floating switch, random press‑time range, detailed debug report

[smga8888]

Description
Feature Overview
Add enable/disable toggle and quick record shortcut button for each action item
Add description text for batch setting switch, plus independent enable/disable toggle for each event
Floating quick‑switch button for scenes
Improve random press‑duration range for click action with input validation
Add more detailed debug report/log export

1. Action list: per‑action enable/disable toggle & quick record button
   Current: There is no toggle to temporarily disable an action without deleting it. Picking click coordinates requires multiple page jumps.
   Proposed:
   Add enable/disable toggle beside each action entry. Disabled action will be skipped during runtime, keep all parameters, UI should be grayed out for disabled items.
   Add quick record icon button on each action item, one‑click to pick screen coordinate directly, no need to enter sub‑page.
   Use case: Convenient for debugging scripts, temporarily skip certain actions without deleting them, reduce operation steps for coordinate picking.
2. Scene page: batch‑setting description & per‑event enable/disable toggle
   Current:
   The batch setting switch lacks descriptive text for users to understand its logic.
   Events cannot be individually enabled or disabled.
   Proposed:
   Show description text beside the batch toggle:
   One‑click to apply "continue execution" to all screen events. Takes effect when all event statuses are consistent; shows off when event statuses are inconsistent.
   Add independent enable/disable toggle for each event entry. Disabled event will not trigger matching, keep configuration. Batch operations only apply to enabled events.
3. Floating quick‑switch button for scenes
   Current: Switching scenes requires navigating to scene list page, tedious during debugging.
   Proposed:
   Add draggable floating "Switch" button.
   Tap floating button to pop‑up scene list, select one scene to switch as active scene.
   Floating button can be hidden or shown in settings, avoid blocking screen operation area.
   Use case: Fast switch between multi‑scene scripts during debugging.
4. Click action: random press duration range with validation
   Current: Random duration toggle exists, but min/max input boxes lack validation.
   Proposed:
   When "Random duration" is enabled, click press time will pick a random integer value between Min duration and Max duration(ms).
   Input validation rules:
   Min duration cannot be greater than max duration.
   Only positive integer millisecond values allowed.
   Give hints or auto‑correct invalid inputs.
   When random duration is off, use fixed press‑duration value.
   Use case: Simulate human‑like click behavior with variable press time.
5. Detailed debug report
   Proposed: Add debug report panel and copy/export log function. Log content includes:
   Total execution count; skip records for disabled actions/events.
   For each click: actual coordinate, real random press time, timestamp.
   Scene matching log: activated scene, match success/failure result and reason for each event.
   Trigger result: executed / skipped‑disabled / skipped‑condition‑not‑met.
   Use case: Help diagnose script not‑working issues, locate configuration or logic problems.
   Compatibility
   All new toggles default to ON. Old script configurations imported from previous versions remain fully compatible, no breaking changes.

功能需求简述
每条动作项增加启用 / 关闭开关，增加快速录制拾取坐标按钮
场景页批量设置增加说明文案，每个事件独立支持启用 / 关闭
悬浮场景快速切换按钮，调试时一键切换场景
单击动作完善随机按压时长范围，增加输入合法性校验
输出更完整的调试报告日志，支持复制导出，记录动作执行、场景匹配、跳过原因
兼容性：所有新增开关默认开启，旧脚本配置完全向后兼容。

[vibhor1102]

Your suggestion all seem useful QoL changes.

I want to specifically discuss the 5th suggestion on the list first, regarding Exporting Debug reports.

What is your use case for exporting debug report, and how would you like it to be? For example, in a machine readable .json format, a pdf, or a screenshot? Or perhaps just saving in app's internal storage and not exporting, viewable from a specific menu from within the app's home page?

I figured that this is a lacking aspect of the debug report, and brainstormed it but couldn't come up with a solution that perfectly fits while i thought for other improvements for the debug report as in #958. And i plan to work on improving the report for v4.1 release

[smga8888]

My main use‑case is self‑testing for events and actions.
I need full detailed runtime information to verify whether behaviours work as expected.
Besides local debugging, I also want to share the debug report with other developers, so they or automated tools can analyse issues and root causes.
For format, JSON is the primary choice. It preserves complete structured runtime data of events/actions, which can be parsed by scripts or other programs.
Workflow expectation:
Generate full debug report including event trigger logs, action execution records, runtime parameters and context data.
Allow exporting the JSON file to user‑accessible storage.
Keep a simple human‑readable preview inside the app for quick check, no need for PDF or screenshot as primary export.

我的主要用途是自测事件与动作的运行情况：
我需要完整的运行详情，用来验证行为是否符合预期。
同时也希望可以把调试报告分享给其他开发者，方便其他人或者自动化工具分析问题、定位根因。
格式优先选 JSON，可以完整保存事件、动作的结构化运行数据，支持脚本 / 机器解析。
期望流程：
生成完整报告，包含事件触发日志、动作执行记录、运行参数、上下文信息。
支持导出 JSON 到用户可访问的存储目录。
App 内部附带简易可读预览即可，不把 PDF、截图作为正式导出格式。