| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
perf: optimize string concatenation performance - Replace str + str with str += to avoid temporary objects - Optimize string concatenation in 26 files across multiple modules - Reduce unnecessary memory allocations and copies Fixes #7134 Co-Authored-By: Agent Signed-off-by: athends <huwanyong1@huawei.com> | 4 个月前 | |
perf: optimize string concatenation performance - Replace str + str with str += to avoid temporary objects - Optimize string concatenation in 26 files across multiple modules - Reduce unnecessary memory allocations and copies Fixes #7134 Co-Authored-By: Agent Signed-off-by: athends <huwanyong1@huawei.com> | 4 个月前 | |
!9804 merge log-downgrade-0715 into master log(mmi): downgrade high-frequency logs to debug and add function-key fields Created-by: kevin812085902 Commit-by: JustinHu Merged-by: openharmony_ci Description: https://gitcode.com/openharmony/multimodalinput_input/issues/7655?ref=&did=4166951#tid-4166951 ## 修改说明 本次为高频日志整改，**仅修改日志级别与日志内容，不涉及任何业务代码**。 ### 一、高频日志降级为 Debug（基于 Domain 0xD002805 Top18 统计） 现网仅采集 Info 及以上日志，Debug 现网不打印。将以下高频日志降为 Debug，可在现网消除刷屏，实验室复现时开启 Debug 仍可观测： | 文件 | 日志 | 改动 | 统计次数 | | --- | --- | --- | --- | | service/joystick/src/joystick_event_interface.cpp | "Device Not joystick" | INFO → DEBUG | 1497 | | service/event_dispatch/src/event_dispatch_handler.cpp | "Can't find pointer item, pointer:-1" | ERROR → DEBUG | 503498 | 说明：pointer 日志 503498 次全部为 pointer:-1（恒为 -1），属稳定的过滤分支而非随机故障，原 ERROR 级别刷屏属级别不当；仅改级别， return 行为不变，不影响业务。 ### 二、维测字段增强（来源于在研维测 diff 的日志部分） 在按键分发/注入日志中追加 NumLock/CapsLock/ScrollLock 功能键状态，便于维测定位： - frameworks/proxy/event_handler/src/client_msg_handler.cpp：按键接收分发日志追加 NL/CL/SL - frameworks/proxy/event_handler/src/input_manager_impl.cpp：按键注入日志追加 NL/CL/SL ### 未纳入修改 - Top18 中 rank2~16（15 条 FingerprintEventProcessor 指纹日志）源码不在本仓，本次未覆盖。 - rank18（CHKFR 宏生成的触屏转换失败 Error 日志）由全仓通用宏生成且为真实功能故障，禁止降级。 ### 自检 - [x] 仅日志改动，无业务逻辑变更 - [ ] CI 编译验证 关联 Issue: 待补充（由提交者手动创建并关联） See merge request: openharmony/multimodalinput_input!9804 | 15 天前 | |
log(mmi): downgrade high-frequency info logs to debug to meet baseline Downgrade roadmark logs (CALL_INFO_TRACE -> CALL_DEBUG_ENTER) and high-frequency info/warn state-flow logs (*I/*W -> *D) to debug level per baseline-governance guideline. Debug logs are gated by HiLogIsLoggable and not printed in release, but remain available when reproducing issues in the lab, so fault-localization capability is preserved. Only log levels are changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
liangwei49@huawei.com Signed-off-by: liangwei <liangwei49@huawei.com> | 10 个月前 | |
liangwei49@huawei.com Signed-off-by: “liangwei” <liangwei49@huawei.com> | 10 个月前 | |
fix log Signed-off-by: Justin_Hu <hugongcheng@huawei.com> | 11 个月前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
Feat:Support Hook For PointerEvent. Co-authored-by: wuliangdong<wuliangdong1@huawei.com> | 9 个月前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
无效头文件删除 Signed-off-by:yang_yong_qi<yangyongqi4@h-partners.com> Signed-off-by: 杨勇琦 <yangyongqi4@h-partners.com> | 1 年前 | |
feat: add inputDevice.bindToDisplay API for binding input devices to displays Add the bindToDisplay API that allows system applications to bind external input devices (USB/Bluetooth) to specific displays. The bound device's events (key and pointer) are routed to the target display. Also improve error codes for SetDisplayBind to return specific codes for display-not-found, device-not-found, and unsupported-device scenarios. The displayId parameter uses int (i32) to match the underlying IPC type. Event dispatch binding is applied via a common ApplyBoundDisplayId function called at each device entry point (mouse/touchpad/joystick/keyboard) before displayId is used for business logic, associating events with the display group of the bound display. Co-Authored-By: Agent 🤖 AI[14%] 🔧 Human Fixed[0%] 🧑 Human[86%] 👌 AI Adopted[100%] Change-Id: I65239653d5a4611fd949587f60b58d3e48f13cc7 Signed-off-by: xueyuanzhao <zhaoxueyuan@huawei.com> Signed-off-by: zhaoxueyuan <zhaoxueyuan@huawei.com> | 1 天前 | |
Add input_feature_touch_gesture Signed-off-by: blueyouth <bailiang18@huawei.com> | 6 个月前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
Fix:Avoid Bad Log. Co-Authored-By:Agent Change-Id: Idfd594616b4763d938f5c178c7dc1918e939549b Signed-off-by: wuliangdong <wuliangdong1@huawei.com> | 2 个月前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
Fix:Fix Bug Of TS Injection Interface. Co-Authored-By:Agent Signed-off-by: wuliangdong <wuliangdong1@huawei.com> | 3 个月前 | |
!9804 merge log-downgrade-0715 into master log(mmi): downgrade high-frequency logs to debug and add function-key fields Created-by: kevin812085902 Commit-by: JustinHu Merged-by: openharmony_ci Description: https://gitcode.com/openharmony/multimodalinput_input/issues/7655?ref=&did=4166951#tid-4166951 ## 修改说明 本次为高频日志整改，**仅修改日志级别与日志内容，不涉及任何业务代码**。 ### 一、高频日志降级为 Debug（基于 Domain 0xD002805 Top18 统计） 现网仅采集 Info 及以上日志，Debug 现网不打印。将以下高频日志降为 Debug，可在现网消除刷屏，实验室复现时开启 Debug 仍可观测： | 文件 | 日志 | 改动 | 统计次数 | | --- | --- | --- | --- | | service/joystick/src/joystick_event_interface.cpp | "Device Not joystick" | INFO → DEBUG | 1497 | | service/event_dispatch/src/event_dispatch_handler.cpp | "Can't find pointer item, pointer:-1" | ERROR → DEBUG | 503498 | 说明：pointer 日志 503498 次全部为 pointer:-1（恒为 -1），属稳定的过滤分支而非随机故障，原 ERROR 级别刷屏属级别不当；仅改级别， return 行为不变，不影响业务。 ### 二、维测字段增强（来源于在研维测 diff 的日志部分） 在按键分发/注入日志中追加 NumLock/CapsLock/ScrollLock 功能键状态，便于维测定位： - frameworks/proxy/event_handler/src/client_msg_handler.cpp：按键接收分发日志追加 NL/CL/SL - frameworks/proxy/event_handler/src/input_manager_impl.cpp：按键注入日志追加 NL/CL/SL ### 未纳入修改 - Top18 中 rank2~16（15 条 FingerprintEventProcessor 指纹日志）源码不在本仓，本次未覆盖。 - rank18（CHKFR 宏生成的触屏转换失败 Error 日志）由全仓通用宏生成且为真实功能故障，禁止降级。 ### 自检 - [x] 仅日志改动，无业务逻辑变更 - [ ] CI 编译验证 关联 Issue: 待补充（由提交者手动创建并关联） See merge request: openharmony/multimodalinput_input!9804 | 15 天前 | |
fix: record all pointer items and free buffer memory on disable - Record every PointerItem's pointerId and toolType in parallel vectors, matching the server-side PushPointerRecord pattern, so multi-touch finger information is preserved in the query result - Restore pointerId on the reconstructed PointerEvent and its items - Free the ring buffer memory in Disable via clear + shrink_to_fit - Add multi-touch unit test covering two PointerItems Co-Authored-By: Agent Signed-off-by: athends <huwanyong1@h-partners.com> AI[100%] Human Fixed[0%] Human[0%] AI Adopted[100%] Co-authored-by: opencode (glm-5.2) <ai@local> | 4 天前 | |
Improve UT coverage Signed-off-by: blueyouth <bailiang18@huawei.com> Change-Id: Ic29bb56990240551cd203047b59227d3eb0c7c0f | 1 年前 | |
fix D i log Signed-off-by: wanghao505 <wanghao505@huawei.com> | 1 年前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
log(mmi): convert remaining CALL_INFO_TRACE function traces to CALL_DEBUG_ENTER CALL_INFO_TRACE emits an Info-level "enter"/"leave" function trace (via InnerFunctionTracer with LOG_INFO), while CALL_DEBUG_ENTER emits the same trace at Debug. Function entry/exit traces are developer diagnostics and should not run at Info in production (the highest-volume ones, e.g. GetProcessName, NotifyBundleName, GetIntervalSinceLastInput, were already migrated). This completes that band by converting every remaining CALL_INFO_TRACE usage to CALL_DEBUG_ENTER, demoting all such traces to Debug. Scope: 505 usage sites across 70 files in service/ (211), intention/ (152), frameworks/ (139), util/ (3). The #define CALL_INFO_TRACE directive in util/common/include/mmi_log.h is preserved (only usages are converted), so the macro still exists for any out-of-tree/test consumer and no redefinition occurs. Safety: the two macros deliberately use distinct tracer variable names (__innerFuncTracer_Debug___ vs ___innerFuncTracer_Info___) so they can coexist. A scope-aware scan (skipping strings/comments) confirmed no scope contains both macros, so renaming cannot create two __innerFuncTracer_Debug___ in one scope. Only the trace-level token is changed; no business logic is touched. TicketNo: (由用户手动关联) Signed-off-by: JustinHu <gchenghu@126.com> Co-Authored-By: Agent | 1 个月前 | |
fix: set raw display coordinates for injected touch events Set RawDisplayX and RawDisplayY when NDK, TS NAPI, and ETS static touch injection entries set display coordinates. This keeps touch white-dot drawing aligned with injected touchscreen coordinates. Fixes #7349 Co-Authored-By: Agent <agent@example.com> Signed-off-by: hellohyh001 <huiyuehong@huawei.com> Change-Id: I80f6386b56772d5475550a9a6523ad50d0af4edf | 2 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 4 个月前 | ||
| 4 个月前 | ||
| 15 天前 | ||
| 1 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 11 个月前 | ||
| 1 个月前 | ||
| 9 个月前 | ||
| 1 个月前 | ||
| 1 年前 | ||
| 1 天前 | ||
| 6 个月前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 2 个月前 | ||
| 1 个月前 | ||
| 3 个月前 | ||
| 15 天前 | ||
| 4 天前 | ||
| 1 年前 | ||
| 1 年前 | ||
| 1 个月前 | ||
| 1 个月前 | ||
| 2 个月前 |