Key Repeats about swift-keylogger HOT 3 CLOSED

In CallBackFunction.swift file:

• From Line 109 to Line 132 deals with the fileName(current active/focused app) and writes the timestamp to that particular app named file

• From Line 133 to Line 162 deals with which key has been pressed and writes that keypress to the file.

In Keylogger.swift file:

• From Line 145 to Line 256 has the mappings of the keyboard keys(QWERTY) corresponding to the keycode(produced in CallBackFunction.swift file From Line 133 to Line 162 ).

from swift-keylogger.

Hi @achalagarwal

I have 2 reasons for not implementing this behaviour.

Reason: 1

I thought of doing it initially but after some googling, I realised it is based on OS behaviour.

On low-level, the system only detects whether a key is pressed or released.

macOS decides what to do based on the settings in Settings.app

This functionality can be done by getting settings data and using timers and if statements.

But, long-pressing a key displays a popup to select accented characters like this:

The accented characters can either be selected by pressing the corresponding number or clicking on the character directly, which can't be detected accurately.

Again, this behaviour can be disabled but only through the terminal like this. But some users prefer getting this popup.

defaults write -g ApplePressAndHoldEnabled -bool false

Implementing all these(timers, preferences etc) would have become too complex for others to extend the functionality based on their needs and also, there is a lot of probability for false positives. So, I decided not to include the functionality.

Reason 2:

Another reason is, as far as I have seen, no one presses the key to type repeated characters, which are meaningful. We only long-press the key when we want to spam a certain character without a proper meaning or to move the cursor or modifier keys. None of them makes sense to log multiple times.

So, making the keylogger's implementation complex just for a very small percentage of users(maybe you might have a proper use-case) seemed completely unnecessary for me.

from swift-keylogger.

Thanks @SkrewEverything

Your points are justified. I would like to modify your implementation to get the key release and key pressed signals.

Do you have an entry function in mind, from where I could start tinkering/digging?

from swift-keylogger.