search

janmechtel / rockettype

A windows keylooger to track typing statistics like WPM
MIT License
3 stars 0 forks source link

Empty stats #30

Closed janmechtel closed 4 years ago

janmechtel commented 4 years ago

  1. Seems like the log file is now stored in %USERPROFILE%\outputs let's change this to %USERPROFILE%\RocketType

  2. My stats are empty:

image

exceptions.txt shows:

""name 'logger_stats' is not defined"" I time i call it

appins commented 4 years ago

For the specific error, could you try uninstalling and reinstalling? Sometimes old files get left / not replaced if you install without uninstalling first. At some point, we should get a better flow for updates and such, but for now, files are moving around constantly.

Let me know if the issue persists, as I am getting no such issue. (also, if you're getting it with the installed version or only the version running out of the repository folder, etc).

janmechtel commented 4 years ago

I haven't tried installing, but now i have this issue when running from debugger.

The RocketType/key_log.txt is created and filled with the header row, but now keys are logged into it after wards.

appins commented 4 years ago

Yes @janmechtel, its a form of caching that is built into operating systems or python. The keystrokes should begin to appear in the file every 60 seconds or so. It might delay the initial collection of stats but massively reduces the amount of time to log keystrokes (Can capture up to >350 WPM, from my tests).

This is a side effect of opening a file and writing to it rather than setting the logger to that file.

janmechtel commented 4 years ago

Ok I will test it now. We should still find a better solution for this, maybe we just ad it to the explanation, as the recommendation in the stats window is to delete the file, which will not help.

Also when I'm debugging sometimes/often the stats window shows immediately, is that intentional?

On Thu, Sep 10, 2020 at 11:13 PM Alex Anderson notifications@github.com wrote:

Yes @janmechtel https://github.com/janmechtel, its a form of caching that is built into operating systems or python. The keystrokes should begin to appear in the file every 60 seconds or so. It might delay the initial collection of stats but massively reduces the amount of time to log keystrokes (Can capture up to >350 WPM, from my tests).

This is a side effect of opening a file and writing to it rather than setting the logger to that file.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/janmechtel/rockettype/issues/30#issuecomment-690734555, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHVGGWULII7QXS3MZ2ATVLSFE6OTANCNFSM4QZGTW6Q .

janmechtel commented 4 years ago

Ok this is working, I was just too impatient for the stats.

On Thu, Sep 10, 2020 at 11:36 PM Jan Mechtel jmechtel@gmail.com wrote:

Ok I will test it now. We should still find a better solution for this, maybe we just ad it to the explanation, as the recommendation in the stats window is to delete the file, which will not help.

Also when I'm debugging sometimes/often the stats window shows immediately, is that intentional?

On Thu, Sep 10, 2020 at 11:13 PM Alex Anderson notifications@github.com wrote:

Yes @janmechtel https://github.com/janmechtel, its a form of caching that is built into operating systems or python. The keystrokes should begin to appear in the file every 60 seconds or so. It might delay the initial collection of stats but massively reduces the amount of time to log keystrokes (Can capture up to >350 WPM, from my tests).

This is a side effect of opening a file and writing to it rather than setting the logger to that file.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/janmechtel/rockettype/issues/30#issuecomment-690734555, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHVGGWULII7QXS3MZ2ATVLSFE6OTANCNFSM4QZGTW6Q .