Using the feedback we got after 2.0.1, we’ve been working on quite a few things of improvement. I am posting this 2.0.2 version only here (not on the main website) see get some feedback from people who have run into issues on the change-log below. If you have indeed run into one of these issues, please try to upgrade to 2.0.2 (just exit the client and install 2.0.2 over your existing 2.0.1) and provide us with feedback. Thanks!
Sadly, after the fix, the network device is listed now, but traffic over the interface still does not count.
I’ve only tested this on my notebook yet. The WLAN adapter is listed too and it’s traffic counts. (I’ve tested it with WLAN disabled to check if LAN counts)
Just installed the new version and the network tracking has definitely improved. However, there are still times where my torrent is uploading @ 1.5mb/s yet WhatPulse says I’m uploading @ half that rate.
It’s just far less random and a bit more accurate than last version which is nice to see.
crashing has increased since update. its on for no more then a minute and it stops responding and crashes. i start it back up again it crashes less then a minute later. ive done this multiple times, now im uninstalling then reinstalling.
Its crashing when i try to pulse. Its Repeatable bug for me.
There is no such thing as DirectX/DirectInput support in listening for events. DirectInput is a way to detect, capture or send input from/to Windows. Windows then sends it to other applications. I saw a previous post where DirectInput was explained as getting the events directly from the hardware, which is not really true. It gets it from a lower level on Windows, same level as the WhatPulse client gets it’s input from.
The client currently gets events when inside games (tested on 7 different platforms, with different games), and has been optimised so it doesn’t get pushed away by another application (like a game).
Downloaded and installed 2.0.2. at my Mac OS X 10.8.2 (Macbook Pro, 15-inch, start of 2011).
My first notice is that the enormous amount of write actions still continues. My HDD is continuesly writing information (This stops when shutting down WhatPulse). I can’t tell if this is worse or less in comparison to version 2.0.1.
My second notice was that the application crashes when manualy pulsing (I’m not using autopulse and have this option disabled). I’ve installed Growl, but it’s not started when I pulse. In 2.0.1. I’ve had the repeating question of selecting the Growl application. Now at 2.0.2. when pulsing and Growl still stopped it crashes (2.0.2. should have improvements on this). When pulsing it starts to do read request (and still write requests) and after about 3 seconds, it’s crashing.
So, at this moment i’m back at version 2.0.1. because I simply can’t pulse