Typing Issues (Event Merging and Incorrect Sequencing)

[BIJJUDAMA]

During fast typing sequences the macro stores a typing sequence note as

keydown n
keyup o
keydown t    <- Problem begins here
keydown e
keyup t
keyup e

It's storing te as a chord instead of seperate typing events.

Probable Causes

• Millisecond Resolution: as_millis() is too coarse; events occurring within the same millisecond are recorded with identical timestamps.
• Lack of Jitter/Gap: 0ms gaps between events trigger OS-level input batching, which target applications interpret as concurrent input.
• Unstable Event Sorting: Events with identical timestamps are not explicitly sorted by their actual delivery order.

Add a wait for keyup logic, where a new keydown event can't occur without the previous keyup completing as well for extra safety